jp_company_resolve — JPVerify MCP Tool
jp_company_resolve
(jp company resolve) is one of 9 tools on the
JPVerify
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call jp_company_resolve from your client
- Claude Code JPVerify jp_company_resolve run in your project directory
- Claude Desktop JPVerify jp_company_resolve ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor JPVerify jp_company_resolve ~/.cursor/mcp.json
- VS Code JPVerify jp_company_resolve .vscode/mcp.json
- Zed JPVerify jp_company_resolve ~/.config/zed/settings.json
- Windsurf JPVerify jp_company_resolve ~/.codeium/windsurf/mcp_config.json
- Cline JPVerify jp_company_resolve ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI JPVerify jp_company_resolve ~/.gemini/settings.json
- Grok JPVerify jp_company_resolve .mcp.json (in your project root)
- ChatGPT JPVerify jp_company_resolve Settings → Connectors → Advanced → Developer mode
- Claude.ai JPVerify jp_company_resolve Settings → Connectors → Add custom connector
- LangChain JPVerify jp_company_resolve pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http jpverify https://api.jpverify.com/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.