Stampchain MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
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
Most tools have distinct purposes targeting different resources (stamps, collections, tokens, market data), but there is some overlap between get_market_data and get_stamp_market_data which could cause confusion. The descriptions clarify that one is general and one is stamp-specific, but the naming similarity might lead to misselection.
Tool names follow a highly consistent verb_noun pattern throughout, with clear prefixes like get_, search_, and analyze_. All use snake_case consistently, making the set predictable and easy to understand at a glance.
With 13 tools, the count is well-scoped for a server focused on Bitcoin stamps, collections, tokens, and market data. Each tool appears to serve a specific function without redundancy, fitting the domain's complexity appropriately.
The tool set covers key operations like retrieval (get_), search, and analysis for stamps, collections, and tokens, with market data features included. Minor gaps might exist, such as no explicit update or delete tools, but these may not be needed for the domain's read-heavy nature, and agents can likely work around this.