arc-pow-sigils-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SITE_URL | No | Base site for /api/image/{id} and /api/meta/{id} links. Default: https://proofofarchitect.builders | https://proofofarchitect.builders |
| ARC_RPC_URL | No | Arc testnet RPC endpoint. Default: https://rpc.testnet.arc.io | https://rpc.testnet.arc.io |
| CRAFT_ADDRESS | No | CraftingController v1 contract address. Default: 0x1542c820cF8644Abb91BF5c275097f89578FC3A9 | 0x1542c820cF8644Abb91BF5c275097f89578FC3A9 |
| CONTRACT_ADDRESS | No | PowMintNFTv3 contract address. Default: 0x2F7cE1e4A175b1A16e4f151fA5B862ea6b9F3C8b | 0x2F7cE1e4A175b1A16e4f151fA5B862ea6b9F3C8b |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| collection_statsA | Read live collection stats from PowMintNFTv3: totalMinted, maxSupply, freeClaims, claimsLeft, claimedCount, currentWave, currentPrice (USDC human units) and mintPaused. |
| get_tokenA | Read a minted token: owner, seed, nonce, tokenURI, plus off-chain image and metadata urls. Returns an error if the token does not exist. |
| required_bitsB | Current PoW difficulty for a miner: requiredBits(miner) as leading zero bits, plus its three layers (wave base, load regulator, active streak) and the wallet's mint count. |
| verify_nonceA | Verify a mined nonce WITHOUT sending a transaction: reads workFor(miner, nonce), counts leading zero bits locally and compares to requiredBits(miner). |
| price_infoA | Explain the pricing: reads currentWave and currentPrice plus epoch config (priceStart 1 USDC, x2 per wave, no cap) and returns a wave summary. |
| craft_infoA | Read-only view of the CraftingController v1 (commit-reveal Architector crafting): paused, craftFee, per-tier boostCost/feeFor/maxChosen (0..3), committedFees, lastCommitId and the reveal/entropy window constants (ENTROPY_DELAY, MIN_REVEAL_DELAY, REVEAL_WINDOW). Also returns the salt policy: preimage = keccak256(abi.encode(SlotChoice[], salt)). |
| verify_craft_commitA | Verify a crafting commit WITHOUT sending a transaction: reads commits(commitId) from the CraftingController, recomputes keccak256(abi.encode(choices, salt)) the same way the contract does, and reports whether it matches the on-chain choicesHash, plus settlement flags, player, boost tier and the reveal window. |
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 7 tools
Each tool targets a distinct read-only concern: collection stats, token lookup, difficulty, pricing, nonce verification, crafting config, and commit verification. Some overlap exists between collection_stats and price_info, since both surface currentWave and currentPrice, but their purposes remain clearly separate.
All names use lowercase snake_case and are readable, but the convention is mixed: get_token and verify_nonce use verb-first naming, while collection_stats, price_info, and craft_info use noun/noun-info patterns, and required_bits is a noun phrase with no verb. This is not chaotic, but it is inconsistent enough to make the set feel less uniform.
With 7 tools, the server is well-scoped for its apparent purpose: reading on-chain PoW minting and crafting state plus verifying miner and commit work. Each tool covers a meaningful concern without redundancy or bloat.
The server covers the core read-only workflows for both minting and crafting: stats, token retrieval, difficulty, pricing, nonce verification, craft config, and commit verification. Minor gaps exist, such as no explicit reveal verification or token listing by owner, but these are not critical dead ends for the server's apparent read-only verification role.