mcp-blockchain-fees
mcp-blockchain-fees is an MCP server published by CryptoAPIs-io, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.
Does mcp-blockchain-fees support the current MCP specification (2026-07-28)?
Not yet confirmed. mcp-blockchain-fees is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is mcp-blockchain-fees a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for mcp-blockchain-fees (as of 2026-08-20).
How do I connect to mcp-blockchain-fees?
mcp-blockchain-fees is available via the package npm:@cryptoapis-io/mcp-blockchain-fees, the official MCP Registry under io.github.CryptoAPIs-io/mcp-blockchain-fees, the source repository at https://github.com/cryptoapis-io/cryptoapis-mcp-blockchain-fees. Authentication: unknown. Transports: stdio.
Does mcp-blockchain-fees support MCP revision 2026-07-28?
No. mcp-blockchain-fees was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
Does mcp-blockchain-fees support MCP revision 2025-11-25?
Yes. mcp-blockchain-fees supports MCP revision 2025-11-25 (checked 2026-08-20).
When were mcp-blockchain-fees's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
MCP server for fee recommendations and gas estimation on EVM, UTXO, XRP, Tezos, Solana
Which MCP spec revisions does mcp-blockchain-fees support?
mcp-blockchain-fees has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2026-07-28 | Not supported | Source | |
| MCP 2025-11-25 | Supported | Source |
How widely adopted is mcp-blockchain-fees?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
Repository and package signals for mcp-blockchain-fees
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Stars
- 0
- Forks
- 0
- Last pushed
- (64 days ago)
- Created
- Open issues
- 0
- Primary language
- TypeScript
- Continuous integration
- None detected
- Tests
- None detected
- Security policy
- None
Declared topics: ai, blockchain, claude, cryptoapis, cursor, evm, fees, gas-estimation, mcp, model-context-protocol, utxo — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
0.4.0- Last published
- First published
- Releases
- 8
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 4
- Unpacked size
- 144 KB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.CryptoAPIs-io/mcp-blockchain-fees at version 0.4.0 - lists package npm:@cryptoapis-io/mcp-blockchain-fees and repository https://github.com/cryptoapis-io/cryptoapis-mcp-blockchain-fees - accessed
- npm registry metadata for @cryptoapis-io/mcp-blockchain-fees at published version 0.4.0, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed