Home / MCP registry index / io.orbitwan/orbitwan

OrbitWan.io

io.orbitwan/orbitwan in the official MCP registry. Endpoint https://mcp.orbitwan.io/mcp.

The registry describes it as: Wanchain explorer and analytics. Premium data: prepaid credit or standard x402 (0.01 USDC/request).

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http orbitwan https://mcp.orbitwan.io/mcp

{
  "mcpServers": {
    "orbitwan": {
      "url": "https://mcp.orbitwan.io/mcp"
    }
  }
}

code --add-mcp '{"name":"orbitwan","type":"http","url":"https://mcp.orbitwan.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

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 find_tagged_addresses get_validator list_validators get_bridge_solvency get_bridge_solvency_live get_earn_yields list_tokens get_contract_creation get_address_summary get_address_flows get_address_ledger get_address_positions get_address_governance get_address_bridge_to_earn list_bridge_to_earn_tasks prepare_bridge_to_earn get_xwan_options get_address_crosschain lookup_selector get_crosschain_stats get_network_stats get_xport_messages get_wan_deflation orbitpay_info orbitpay_crosschain_history orbitpay_economics_series orbitpay_token_supplies get_token_prices get_address_holdings orbitpay_tags_export orbitpay_vault

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-30): 8c6f2b09fa127adb. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-orbitwan-orbitwan/badge.svg)](https://lazaretto.dev/mcp-registry/io-orbitwan-orbitwan)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers · Analytics and SEO MCP servers