orbit-apiofficial
F
licenseNot graded
qualityD
maintenanceMCP server for cross-chain bridging, enabling AI agents to find routes, estimate costs, check risks, execute transfers, and track status across blockchains.
-
ArcLeap MCP
Related Servers
Alternatives to ArcLeap MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server that lets any AI agent operate a wallet directly on-chain: create wallets, send, swap, bridge, and deploy contracts across EVM and Bitcoin networks.2MIT
- AlicenseAqualityDmaintenanceAn MCP server for USDC payments on Base, enabling AI agents to check balances, send payments, generate payment requests, and view transaction history.41MIT
- AlicenseAqualityCmaintenanceMCP server for Circle's Agent Stack. Create wallets, set spend policies, send USDC, and pay x402-priced endpoints — all from a tool call.623 npm1MIT
- AlicenseNot gradedqualityAmaintenanceNon-custodial BVCC Agent Wallet MCP server: let an AI agent check balances, send native/ERC-20, approve, and swap on Uniswap v3/v4 across Ethereum, BNB Chain, Arbitrum and Base, within on-chain enforced limits.96 npm2MIT
- FlicenseNot gradedqualityBmaintenanceA zero-dependency MCP server that bridges AI agents to Robinhood Chain and Arbitrum Orbit L2 networks, enabling querying balances, simulating transactions, and signing/broadcasting EVM transactions via JSON-RPC tools.6-
TDQS
A3.8/5.0
Scored across 6 tools
Disambiguation5/5
Each tool targets a distinct operation: bridge_start initiates a transfer, bridge_status completes it, bridge_history lists past transfers, bridge_wallet_info shows wallet details, bridge_list_chains lists supported networks, and bridge_quote checks routes. There's no overlap between these purposes, and the descriptions clearly explain the call flow and when each should be used.
Naming Consistency5/5
All tools follow a consistent 'bridge_' prefix with a clear noun indicating the resource or action (start, status, history, wallet_info, list_chains, quote). The verb_noun pattern is uniform throughout, making the naming predictable even for agents unfamiliar with the server.
Tool Count5/5
Six tools is well-scoped for a bridging service: coverage of start, completion, history, wallet info, chain list, and quote/preflight check. Each tool earns its place and none feel redundant or unnecessary for the domain.
Completeness4/5
The tool surface covers the full lifecycle of a cross-chain transfer: quoting/preflight, initiation, completion, and history/journal. Minor gaps exist, such as no explicit cancel/revert operation or gas management tool, but the core bridging workflow is fully covered with no dead ends.
Maintenance
ActivitySlowing
ResponsivenessNo issues