resolve_issuer — getticker: the Ticker door MCP Tool Read-only
resolve_issuer
(resolve issuer) is one of 3 tools on the
getticker: the Ticker door
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call resolve_issuer from your client
- Claude Code getticker: the Ticker door resolve_issuer run in your project directory
- Claude Desktop getticker: the Ticker door resolve_issuer ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor getticker: the Ticker door resolve_issuer ~/.cursor/mcp.json
- VS Code getticker: the Ticker door resolve_issuer .vscode/mcp.json
- Zed getticker: the Ticker door resolve_issuer ~/.config/zed/settings.json
- Windsurf getticker: the Ticker door resolve_issuer ~/.codeium/windsurf/mcp_config.json
- Cline getticker: the Ticker door resolve_issuer ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI getticker: the Ticker door resolve_issuer ~/.gemini/settings.json
- Grok getticker: the Ticker door resolve_issuer .mcp.json (in your project root)
- ChatGPT getticker: the Ticker door resolve_issuer Settings → Connectors → Advanced → Developer mode
- Claude.ai getticker: the Ticker door resolve_issuer Settings → Connectors → Add custom connector
- LangChain getticker: the Ticker door resolve_issuer pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http getticker https://mcp.getticker.ai/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 5 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.