verify_passport — Joy Trust Network MCP Tool
verify_passport
(verify passport) is one of 31 tools on the
Joy Trust Network
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call verify_passport from your client
- Claude Code Joy Trust Network verify_passport run in your project directory
- Claude Desktop Joy Trust Network verify_passport ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Joy Trust Network verify_passport ~/.cursor/mcp.json
- VS Code Joy Trust Network verify_passport .vscode/mcp.json
- Zed Joy Trust Network verify_passport ~/.config/zed/settings.json
- Windsurf Joy Trust Network verify_passport ~/.codeium/windsurf/mcp_config.json
- Cline Joy Trust Network verify_passport ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Joy Trust Network verify_passport ~/.gemini/settings.json
- Grok Joy Trust Network verify_passport .mcp.json (in your project root)
- ChatGPT Joy Trust Network verify_passport Settings → Connectors → Advanced → Developer mode
- Claude.ai Joy Trust Network verify_passport Settings → Connectors → Add custom connector
- LangChain Joy Trust Network verify_passport pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http joy https://joy-connect.fly.dev/mcp
Other tools on this server
- discover_agents
- get_agent
- network_stats
- list_capabilities
- get_trust_score
- verify_trust
- get_passport
- list_platforms
- issue_passport
- create_stake
- resolve_stake
- get_stakes
- get_wallet
- create_topup_link
- create_payment_deal
- list_deals
- complete_deal
- list_jobs
- post_job
- claim_job
- submit_job
- approve_job
- create_ticket
- get_ticket
- get_org_dashboard
- list_campaigns
- create_campaign
- list_audits
- buzz_can
- buzz_bind
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.