Stampchain MCP Server
Related Servers
Alternatives to Stampchain MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables interaction with Bitcoin Stamps data via the Stampchain API, providing tools for querying stamp information, collections, and blockchain data without requiring authentication.13MIT
- AlicenseBqualityCmaintenanceEnables AI agents to explore Bitcoin Stamps data—stamps, SRC-20 tokens, SRC-101 names, collections, dispensers, and wallet balances—via 24 read-only tools over the stampchain.io API, with no keys or wallet access.24MIT
- FlicenseAqualityDmaintenanceEnables MCP-compatible clients to query the RustChain blockchain, check balances, list miners, view epoch info, check network health, transfer RTC, and browse recent transactions and bounties.7-

fletch-mcpofficial
AlicenseBqualityBmaintenanceEnables MCP clients to query Robinhood Chain registry data, including verified stock token addresses, live token state, Chainlink feed rounds, holders, pools, bridge activity, and issuer documents.1739MIT- AlicenseAqualityDmaintenanceProvides read-only access to Solana on-chain data, enabling natural language queries for wallet balances, token holdings, prices, transactions, and more via MCP-compatible clients.8MIT
- FlicenseNot gradedqualityBmaintenanceExposes 8 read-only Trust Vault tools over MCP (Streamable HTTP) for querying protocol overview, tokens, market rates, orders, platform stats, fees, and currencies. Enables on-chain reads and static config without wallet or signing.-
TDQS
Scored across 13 tools
Several tools have unclear boundaries: get_stamp_market_data and get_market_data both cover market data, and analyze_stamp_code's dependency resolution overlaps heavily with get_stamp_dependencies. An agent could easily select the wrong tool for recursive-stamp analysis or market queries.
Tool names mostly follow a consistent get_/search_/analyze_ + noun pattern, with no mixed casing. Minor inconsistencies like get_stamp_market_data vs get_market_data and get_stamp_dependencies vs the analyze_ prefix for similar functions keep it from being perfect.
Thirteen tools is a reasonable size for an explorer/analytics server covering stamps, collections, tokens, and recursive code analysis. However, a few near-duplicate market-data and dependency tools could be consolidated without losing functionality.
The surface covers the main read/query workflows for stamps, collections, SRC-20 tokens, sales, market data, and recursive-stamp analysis. Obvious gaps are minor for a read-only API, such as no per-sale lookup or nested collection-stamp listing, but agents can complete most tasks.