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