get_api_v1_search — nameresolver MCP Tool Read-only
get_api_v1_search
(get api v1 search) is one of 1 tool on the
nameresolver
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_api_v1_search from your client
- Claude Code nameresolver get_api_v1_search run in your project directory
- Claude Desktop nameresolver get_api_v1_search ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor nameresolver get_api_v1_search ~/.cursor/mcp.json
- VS Code nameresolver get_api_v1_search .vscode/mcp.json
- Zed nameresolver get_api_v1_search ~/.config/zed/settings.json
- Windsurf nameresolver get_api_v1_search ~/.codeium/windsurf/mcp_config.json
- Cline nameresolver get_api_v1_search ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI nameresolver get_api_v1_search ~/.gemini/settings.json
- Grok nameresolver get_api_v1_search .mcp.json (in your project root)
- ChatGPT nameresolver get_api_v1_search Settings → Connectors → Advanced → Developer mode
- Claude.ai nameresolver get_api_v1_search Settings → Connectors → Add custom connector
- LangChain nameresolver get_api_v1_search pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http nameresolver https://mcp.jojapi.com/nameresolver
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.