Skip to main content
Glama
arc-pow-sigils-mcp

arc-pow-sigils-mcp

arc-pow-sigils-mcp

A standalone Model Context Protocol (MCP) server for the Proof of Architect NFT collection (deterministic Architector cards) — a proof-of-work minted NFT on Arc mainnet (chainId 5042, native gas token USDC, 18 decimals).

The server exposes read-only tools over the deployed PowMintNFTv3 contract so an LLM agent can inspect collection stats, token data, PoW difficulty and pricing — and even verify a mined nonce without sending a transaction.

  • Contract (v3.4 mainnet): 0x3E20bb7be2C46f94Cab78d340D3F79Afc2a9Fed4 (Arc mainnet; override via CONTRACT_ADDRESS)

  • RPC: https://rpc.mainnet.arc.io (override via ARC_RPC_URL)

  • Transport: stdio (newline-delimited JSON-RPC)


Quick start

Run with npx (after publishing)

npx arc-pow-sigils-mcp

Run from source

npm install
npm run build      # tsc -> dist/
npm run smoke      # spawns the server and hits the live chain
node dist/index.js # start the stdio server

The server speaks MCP over stdin/stdout and logs only to stderr — it is normally launched by an MCP client, not by hand.


Related MCP server: not-for-humans-mcp

Use in Claude Desktop

Add this to your claude_desktop_config.json (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):

{
  "mcpServers": {
    "arc-pow-sigils": {
      "command": "npx",
      "args": ["-y", "arc-pow-sigils-mcp"],
      "env": {
        "SITE_URL": "https://proofofarchitect.builders"
      }
    }
  }
}

Or, pointing at a local build:

{
  "mcpServers": {
    "arc-pow-sigils": {
      "command": "node",
      "args": ["/absolute/path/to/mcp/dist/index.js"],
      "env": {
        "CONTRACT_ADDRESS": "0x3E20bb7be2C46f94Cab78d340D3F79Afc2a9Fed4",
        "ARC_RPC_URL": "https://rpc.mainnet.arc.io",
        "SITE_URL": "https://proofofarchitect.builders"
      }
    }
  }
}

Restart Claude Desktop after editing the config.


Tools

Tool

Input

Returns

collection_stats

—

totalMinted, maxSupply, freeClaims, claimsLeft, claimedCount, currentWave, currentPrice (wei + USDC), mintPaused

get_token

tokenId (number)

owner, raw seedOf, displaySeed (post-inclusion seed that drives traits/art), mintBlock, pending, nonce, tokenURI, off-chain image + metadata urls. Error content if the token doesn't exist.

required_bits

miner (address)

requiredBits (display leading zero bits), requiredMilli (v3.4 milli-bits), the exact target, plus the wave/loadAdjust/streakBits breakdown. Three difficulty layers: base 30 + 2 bits per wave, a pace regulator, and a per-wallet streak (+2 bits per extra mint inside the cooldown window = 60 s × wave); a staking discount is applied in milli-bits.

verify_nonce

miner (address), nonce (uint256 decimal string)

work, target, valid — verifies a mined nonce without a transaction (valid iff uint256(work) < target).

price_info

—

currentPrice + wave math (epoch size 1000, priceStart 1.0 USDC, x2 per wave, no cap — 15 waves, last wave 16 384 USDC).

craft_info

—

CraftingControllerV2 config (one-shot model): paused, craftFee, and per-tier boostCost/feeFor/maxChosen (tiers 0..3). Each craft is a single payable transaction — there is no commit/reveal step, no refund, and no salt.

All tools return a single JSON text content block. verify_nonce recomputes the preimage hash locally as keccak256(abi.encodePacked(chainId, contract, miner, nonce)) and checks it against the wallet's on-chain targetFor — so it does not trust the RPC for the PoW verdict.

Example: verify a mined nonce

Sample response for a placeholder wallet on the current mainnet core (CONTRACT_ADDRESS, as of 2026-09):

{
  "miner": "0x1111111111111111111111111111111111111111",
  "nonce": "1024085",
  "work": "0x0abff08ab4b0e81f9f54ff18d6ae1ecf695c2b7eca20527a80e3dfa3da6801d6",
  "workMatchesOnChain": true,
  "target": "107839786668602559178668060348078522694548577690162289924414440996864",
  "valid": false
}

Call it as verify_nonce(miner = "0x1111111111111111111111111111111111111111", nonce = "1024085"). The PoW formula is the same across instances — the contract address binds the preimage, so pass nonces mined for the contract you query. valid is checked against the current fractional target; a nonce mined before a wave escalation or regulator tightening may no longer pass.


Environment variables

Variable

Default

Purpose

CONTRACT_ADDRESS

0x3E20bb7be2C46f94Cab78d340D3F79Afc2a9Fed4

PowMintNFTv3_4 address (Arc mainnet canon)

CRAFT_ADDRESS

0xb7f32811F19579D9FC6F0e5ac925473554091a91

CraftingControllerV2 address (one-shot crafting)

ARC_RPC_URL

https://rpc.mainnet.arc.io

Arc RPC endpoint. A comma-separated list is accepted; endpoints are tried in order (viem fallback).

ARC_CHAIN_ID

5042

Arc chain id (set 5042002 for testnet).

ARC_EXPLORER_URL

https://explorer.arc.io

Block explorer base URL.

ARC_IS_TESTNET

false

Set to true for the testnet.

SITE_URL

https://proofofarchitect.builders

Base site for /api/image/{id} and /api/meta/{id} links

All variables are optional. No secrets are read or stored.


Publish to the MCP registry

  1. Check the registry name. The official MCP registry requires a reverse-DNS server name that includes your GitHub username. This package is already set to io.github.Proofofarchitect/arc-pow-sigils in both package.json (mcpName field) and server.json (name field) — keep them in lockstep.

  2. Publish the npm package (the registry resolves the stdio package by name):

    npm run build
    npm publish --access public
  3. Install the registry publisher CLI and publish the server metadata (requires the GitHub account Proofofarchitect for the namespace check):

    npx @modelcontextprotocol/mcp-publisher --help
    
    npx @modelcontextprotocol/mcp-publisher init      # scaffolds/validates server.json
    npx @modelcontextprotocol/mcp-publisher login github   # auth with your GitHub account
    npx @modelcontextprotocol/mcp-publisher publish   # publishes server.json

    The publisher verifies that the name namespace matches your authenticated GitHub identity (that is why the placeholder must be replaced).

  4. Verify on the registry at registry.modelcontextprotocol.io. New entries are served with preview status while the registry is in preview.

Keep package.json version and server.json version (and the package version field) in lockstep on every release.


Development

src/chain.ts   viem client singleton (env-driven chain + RPC failover), contract
               read helpers, milli-bit target checks, USDC formatting, work hash
src/index.ts   McpServer + 6 registered tools over StdioServerTransport
smoke.mjs      minimal newline-delimited JSON-RPC client used by `npm run smoke`
server.json    MCP registry manifest (npm stdio)

The ABI is embedded in this package (see src/chain.ts) — it is not imported from the website package, so mcp/ stays independently publishable.

License

MIT

Available Tools

7 tools
collection_statsCollection statsA

Read live collection stats from PowMintNFTv3: totalMinted, maxSupply, freeClaims, claimsLeft, claimedCount, currentWave, currentPrice (USDC human units) and mintPaused.

Inputs: no named parameters.

craft_infoCraft 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)).

Inputs: no named parameters.

get_tokenGet 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.

Inputs: tokenId (required).

price_infoPrice infoA

Explain the pricing: reads currentWave and currentPrice plus epoch config (priceStart 1 USDC, x2 per wave, no cap) and returns a wave summary.

Inputs: no named parameters.

required_bitsRequired 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.

Inputs: miner (required).

verify_craft_commitVerify 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.

Inputs: salt (required), choices (required), commitId (required).

verify_nonceVerify nonceA

Verify a mined nonce WITHOUT sending a transaction: reads workFor(miner, nonce), counts leading zero bits locally and compares to requiredBits(miner).

Inputs: miner (required), nonce (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 7 tools

    Disambiguation4/5

    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.

    Naming Consistency3/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers