swiftnodes-mcpofficial
A
licenseA
qualityB
maintenanceEnables AI agents to retrieve multi-chain RPC details, live pricing, weekly-probed JSON-RPC method support, and probe any EVM endpoint for diagnostics.
5
7 npm
MIT
horizen-mcp
OfficialRelated Servers
Alternatives to horizen-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides grounded chain facts and build patterns for Rome Protocol, enabling agents to access live registry data and SDK patterns read-only.1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to fetch and independently verify on-chain data such as account balances and contract code hashes using Merkle proofs and ECDSA signatures, with x402 payment integration.3MIT
z1n-mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to read Z1N Protocol identity data on Polygon mainnet, including protocol state, keys, signals, and attestation windows, while supporting local deterministic transaction encoding and verification of on-chain vs indexed deltas.10 npmMIT- AlicenseNot gradedqualityAmaintenanceEnables AI agents to query cryptographically verified facts with zero-knowledge proofs, selective disclosure, and tamper-evident provenance.192 npm1Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA comprehensive toolkit for building AI agents with blockchain capabilities, enabling interactions with multiple blockchain networks for tasks like wallet management, fund transfers, smart contract interactions, and cross-chain asset bridging.4GPL 3.0
TDQS
A4/5.0
Scored across 9 tools
Disambiguation5/5
Each tool targets a clearly distinct resource or action: chain metadata, integration info, contract addresses/registry, Stork feed IDs/prices, bridge info, token specs, and zkVerify proof status. Even related Stork and contract tools are separated cleanly and described without ambiguity.
Naming Consistency5/5
All tool names follow a snake_case action_noun pattern, predominantly get_<entity>_info or get_<entity>_address. The list_, fetch_, and check_ deviations are semantically justified for listing, live API pulls, and verification, so the naming remains predictable and consistent.
Tool Count5/5
With 9 tools, the server is well-scoped for its purpose: chain metadata, integration info, contract registry, bridge info, tokens, Stork oracle, and zkVerify each have a dedicated tool. There is no obvious redundancy or bloat.
Completeness5/5
The surface covers the main Horizen ecosystem information needs: network metadata, registry addresses, token details, bridge info, Stork feed ID/price, and zkVerify verification. It includes multi-network support, explicit not-found semantics, and no obvious dead ends or missing operations.
Maintenance
ActivityMaintained
ResponsivenessNo issues