resolve_issuer — getresearch: the Data Research door MCP Tool Read-only
resolve_issuer
(resolve issuer) is one of 3 tools on the
getresearch: the Data Research 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 getresearch: the Data Research door resolve_issuer run in your project directory
- Claude Desktop getresearch: the Data Research door resolve_issuer ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor getresearch: the Data Research door resolve_issuer ~/.cursor/mcp.json
- VS Code getresearch: the Data Research door resolve_issuer .vscode/mcp.json
- Zed getresearch: the Data Research door resolve_issuer ~/.config/zed/settings.json
- Windsurf getresearch: the Data Research door resolve_issuer ~/.codeium/windsurf/mcp_config.json
- Cline getresearch: the Data Research door resolve_issuer ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI getresearch: the Data Research door resolve_issuer ~/.gemini/settings.json
- Grok getresearch: the Data Research door resolve_issuer .mcp.json (in your project root)
- ChatGPT getresearch: the Data Research door resolve_issuer Settings → Connectors → Advanced → Developer mode
- Claude.ai getresearch: the Data Research door resolve_issuer Settings → Connectors → Add custom connector
- LangChain getresearch: the Data Research door resolve_issuer pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http getresearch https://mcp.getresearch.ai/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.