mcp-address-history
mcp-address-history 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-address-history support the current MCP specification (2026-07-28)?
Not yet confirmed. mcp-address-history 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-address-history a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for mcp-address-history (as of 2026-08-20).
How do I connect to mcp-address-history?
mcp-address-history is available via the package npm:@cryptoapis-io/mcp-address-history, the official MCP Registry under io.github.CryptoAPIs-io/mcp-address-history, the source repository at https://github.com/cryptoapis-io/cryptoapis-mcp-address-history. Authentication: unknown. Transports: stdio.
Does mcp-address-history support MCP revision 2025-11-25?
Yes. mcp-address-history supports MCP revision 2025-11-25 (checked 2026-08-20).
Does mcp-address-history support MCP revision 2026-07-28?
No. mcp-address-history was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were mcp-address-history's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
MCP server for full transaction and token history on EVM and UTXO addresses via Crypto APIs
Which MCP spec revisions does mcp-address-history support?
mcp-address-history 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 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is mcp-address-history?
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-address-history
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: address, ai, blockchain, claude, cryptoapis, cursor, evm, mcp, model-context-protocol, transactions, utxo — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
0.3.1- Last published
- First published
- Releases
- 8
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 4
- Unpacked size
- 388 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-address-history at version 0.3.1 - lists package npm:@cryptoapis-io/mcp-address-history and repository https://github.com/cryptoapis-io/cryptoapis-mcp-address-history - accessed
- npm registry metadata for @cryptoapis-io/mcp-address-history at published version 0.3.1, 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