orbitpay_vault — OrbitWan.io MCP Tool
orbitpay_vault
(orbitpay vault) is one of 27 tools on the
OrbitWan.io
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call orbitpay_vault from your client
- Claude Code OrbitWan.io orbitpay_vault run in your project directory
- Claude Desktop OrbitWan.io orbitpay_vault ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor OrbitWan.io orbitpay_vault ~/.cursor/mcp.json
- VS Code OrbitWan.io orbitpay_vault .vscode/mcp.json
- Zed OrbitWan.io orbitpay_vault ~/.config/zed/settings.json
- Windsurf OrbitWan.io orbitpay_vault ~/.codeium/windsurf/mcp_config.json
- Cline OrbitWan.io orbitpay_vault ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI OrbitWan.io orbitpay_vault ~/.gemini/settings.json
- Grok OrbitWan.io orbitpay_vault .mcp.json (in your project root)
- ChatGPT OrbitWan.io orbitpay_vault Settings → Connectors → Advanced → Developer mode
- Claude.ai OrbitWan.io orbitpay_vault Settings → Connectors → Add custom connector
- LangChain OrbitWan.io orbitpay_vault pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http orbitwan https://mcp.orbitwan.io/mcp
Other tools on this server
- get_chain_status
- resolve_identifier
- get_address_activity
- get_transaction
- get_bridge_activity
- get_chain_coverage
- get_token
- get_verified_contract
- list_verified_contracts
- get_address_tags
- get_validator
- get_bridge_solvency
- get_earn_yields
- list_tokens
- get_contract_creation
- get_address_summary
- get_address_flows
- get_address_positions
- get_address_governance
- lookup_selector
- get_crosschain_stats
- orbitpay_info
- orbitpay_crosschain_history
- orbitpay_economics_series
- orbitpay_token_supplies
- orbitpay_tags_export
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.