spirit-cards-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPIRIT_CARDS_API | No | Base URL of the hosted site/API | https://spiritcards.fun |
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 | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_project_infoA | Fetch the Spirit Cards machine-readable project descriptor (/.well-known/ai.json) plus a human summary of the game. |
| get_collection_statsA | Live collection stats (/stats/current.json): supply, price, required PoW bits, cooldown, paused flag. |
| get_cardC | Fetch on-chain card metadata for a tokenId (/api/meta/{tokenId}). |
| get_leaderboardB | Fetch the points leaderboard (/api/points), trimmed to |
| get_recent_activityC | Fetch recent on-chain events (/api/recent), trimmed to |
| get_poolA | Fetch the live staking-pool / emissions snapshot (/api/pool): accrued pool and house revenue, the fee split shares, and the vault's total weight and undistributed rewards. |
| verify_nonceA | Locally compute keccak256(chainId || core || miner || nonce) and check whether its leadingZeroBits reaches the live required difficulty. Read-only; no transaction is sent. |
| find_nonceA | Grind nonce = 0,1,2,... locally until leadingZeroBits(work) >= the live required difficulty. Bounded by maxAttempts (default 1,000,000, hard cap 5,000,000) and a ~20s wall-clock cap. Read-only; returns the nonce to submit to mine(); it does not send a transaction. |
| get_mining_guideA | Step-by-step guide to mint a Spirit Card: the PoW rule, live difficulty/price/cooldown, the exact contract call, and where to get the miner. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| project_overview | Introduce Spirit Cards to a newcomer. |
| start_mining | Guide the user through finding a nonce and minting a card. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct endpoint or action: info, stats, card metadata, leaderboard, activity, pool, and PoW helpers. verify_nonce and find_nonce are closely related but clearly differentiated (check a given nonce vs. grind for one), and the read-only guide is distinct from all data fetches. Minor potential overlap between get_collection_stats and get_pool, but descriptions keep them separable.
Eight of nine tools follow a predictable verb_noun snake_case pattern (get_*, verify_*, find_*), using get_ for data retrieval and action verbs for computations. Fully consistent and readable throughout.
Nine tools is well-scoped for a read/query plus PoW-helper server. Each tool maps to a discrete endpoint or computation, with no redundant fillers.
Covers the read surface thoroughly (project, stats, card, leaderboard, activity, pool) plus the full PoW workflow (verify, find, guide). The notable gap is a submit/mint operation to actually send the mined nonce to mine(), though the read-only design is stated deliberately and the guide explains the external call.