Stampchain MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STAMPCHAIN_API_URL | No | API base URL. | https://stampchain.io/api |
| STAMPCHAIN_LOG_LEVEL | No | Logging level (debug, info, warn, error). | |
| STAMPCHAIN_API_TIMEOUT | No | API timeout in milliseconds. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {
"subscribe": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_stampC | Retrieve detailed information about a specific Bitcoin stamp by its ID |
| search_stampsC | Search for Bitcoin stamps with various filtering criteria including creator, collection, and stamp type |
| get_recent_stampsC | Retrieve the most recently created Bitcoin stamps |
| get_recent_salesC | Retrieve recent stamp sales with enhanced transaction details (v2.3 feature) |
| get_market_dataC | Retrieve market data for stamps with trading activity indicators (v2.3 feature) |
| get_stamp_market_dataC | Retrieve detailed market data for a specific stamp (v2.3 feature) |
| get_collectionB | Retrieve detailed information about a specific stamp collection by its ID |
| search_collectionsC | Search for stamp collections with various filtering criteria |
| get_token_infoC | Retrieve detailed information about a specific SRC-20 token by its ticker symbol |
| search_tokensC | Search for SRC-20 tokens with various filtering criteria |
| analyze_stamp_codeC | Analyze the code structure and dependencies of a recursive stamp, including JavaScript parsing, dependency resolution, and pattern detection |
| get_stamp_dependenciesB | Create a hierarchical dependency graph for a recursive stamp, showing all referenced stamps and their relationships |
| analyze_stamp_patternsC | Analyze patterns across multiple recursive stamps to identify common libraries, frameworks, and coding techniques used in the ecosystem |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.