MCP Scorecard

Mission StatementGitHub
← All posts

Crypto Finds MCP: Three Blockchain Servers in One Batch

A $5.5M-funded cross-chain protocol, a zkSync development toolkit, and a privacy-preserving on-chain verifier all registered MCP servers in the same scan. DeFi is treating agent interfaces as infrastructure.
io.github.debridge-financeio.github.Jrigadaio.github.douglasborthwick-crypto

Three of eleven new servers in this scan are blockchain projects. That's 27% of the batch from a sector that had almost no MCP presence a week ago. Each comes at the problem from a different angle, and together they outline how crypto is approaching agent tooling.

deBridge: Venture-Backed Cross-Chain Swaps

io.github.debridge-finance/debridge-mcp is the heavyweight. deBridge is a cross-chain interoperability protocol that raised $5.5 million in seed funding led by ParaFi Capital, with participation from Animoca Brands, Crypto.com Capital, and 40+ other investors. Co-founded by Alex Smirnov, the protocol enables cross-chain swaps and transfers across 20+ blockchains. Their MCP server lets AI agents find optimal swap routes, check fees, and initiate trades — 25 GitHub stars already, TypeScript, MIT-licensed, Docker-ready, with integration guides for Claude Code, Cursor, Windsurf, and five other MCP clients.

Score: 62. No flags. This is a well-funded protocol team treating MCP as a first-class integration channel, not an afterthought.

foundry-zksync: Smart Contract Tooling for ZK Rollups

io.github.Jrigada/foundry-zksync wraps the foundry-zksync CLI — the standard development toolkit for zkSync, Ethereum's leading ZK rollup. Built by Jrigada, it exposes 21 tools for compiling, testing, deploying, and verifying smart contracts through natural language. The standout detail: a built-in knowledge base of 45+ entries covering zkSync-specific gotchas and edge cases. Security-conscious key management too — hardware wallets, cloud KMS (AWS, GCP), and encrypted keystores instead of passing private keys through MCP parameters. 133 tests.

Score: 56. Created February 23, 2026 — brand new but architecturally serious.

Insumer: Privacy-Preserving On-Chain Verification

io.github.douglasborthwick-crypto/insumer takes a different angle entirely. Instead of trading or deploying, Insumer lets AI agents verify on-chain conditions — token balances, NFT ownership, multi-chain logic — across 31 blockchains (30 EVM + Solana) without exposing wallet balances or private data. ECDSA-signed attestation results. A credit system (1 USDC = 25 credits) and a merchant onboarding flow suggest this is aimed at commerce: prove you hold the token, get the discount, skip the KYC.

Score: 51. JavaScript, MIT-licensed, newly registered.

The Pattern

What connects these three isn't just blockchain — it's the bet that AI agents will become primary interfaces for on-chain operations. deBridge wants agents to route trades. foundry-zksync wants agents to deploy contracts. Insumer wants agents to verify holdings. Each is building for a world where the human doesn't interact with the blockchain directly — the agent does, through MCP.

This mirrors what happened with IOWarp and scientific computing: a specialized domain where the tooling is powerful but the interfaces are hostile, and MCP shows up as the abstraction layer that makes agent mediation possible. DeFi's CLI and API sprawl — dozens of chains, each with their own RPC, wallet formats, and transaction semantics — is exactly the kind of complexity that benefits from a protocol-level agent interface. Expect more. The crypto builders move fast, and MCP just became a surface they can ship to.

Data sourced from the MCP Registry via MCP Scorecard. Trust scores computed from observable signals only.

← Registry Pulse: 123 New Servers in 24 HoursClaude Learns to DJ →