Touchstone MCP server
online · 96% uptimeio.github.petrkrulis2022/touchstone-mcp·v0.1.0Dated SIU, the benchmark price of AI inference work: one free tool, three paid via x402.
0 stars
Reviews
Write oneNobody has reviewed Touchstone yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Touchstone tools (4)
write = sends, deletes, buys or postsconvertFreeConvert a model call's token counts into SIU and USD.
get_indexFreeThe signed Dated SIU print. Free — citation is the business.
get_quoteFreeSIU price, exchange rate and index refs for one task class and model.
verify_receiptFreeReads an on-chain settlement and returns a signed attestation.
Public scan report
scanner v0.1.10 · 2026-10-29 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 7609ms12/20
- Tool poisoning4 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Touchstone compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 80/100
- higher than 60% of 48,243 servers
- Tools
- 4
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 96%
- of our recent checks; the typical remote server answers 100%
- Response time
- 1,698 ms
- faster than 5% of 30,027 servers
What its tools let an agent do: 4 read
Install Touchstone in Claude Code, Cursor or VS Code
claude mcp add --transport http touchstone-mcp https://mcp.touchstoneassay.com/mcp
What the publisher says
From the Touchstone repository's README, as published. We do not edit it. Read it on GitHub
Touchstone Assay
Touchstone Assay publishes Dated SIU — the benchmark price of AI inference work, measured by actually buying inference against a versioned task basket, not by surveying list prices.
The two hard invariants
rates and are never inputs to the print.
- The print is computed from executed runs only. Published list prices inform exchange
the buyer, or to the fee treasury — no admin path to user money exists in any code path.
- The escrow contract is non-custodial. Funds move only to the pre-agreed seller, back to
How to run a print
Placeholder — wired up once packages/print exists.
Docs
agent loop, real transcripts, on Base Sepolia and Arc Testnet.
- CLAUDE.md — vocabulary, invariants, build boundaries.
- docs/build1-spec.md — the Build 1 engineering specification.
- docs/plan.md — orientation, dependency order, and open risks.
- docs/architecture.md — one diagram of the whole system.
- docs/demo.md / docs/demo-arc.md — the buyer/seller
Deployments
<!-- BEGIN GENERATED: deployments -->
Arc Testnet
Chain ID 5042002. Deployed 2026-09-05 from commit 95eea03.
Full record — transaction hashes, block numbers, constructor arguments, compiler settings, and live smoke-test results — is canonical in data/deployments/arc-testnet.json. This README section is a convenience view generated from that file (node scripts/generate-readme-deployments.mjs) and must never be hand-edited to disagree with it.
Not deployed to mainnet. Requirements before it can be:
- treasury MUST be a Safe/multisig, not an EOA. It is immutable with no setter, so a lost key makes fee revenue permanently unrecoverable and the only remedy is redeploying the escrow and migrating every integrator.
- Generate TOUCHSTONEPUBLISHERKEY on an air-gapped machine. The testnet key reused here has passed through repository-adjacent files.
- DeployArcTestnet.s.sol is chain-guarded to 5042002; a mainnet deployment needs its own script and its own review.
- Arc mainnet's own chain ID and USDC contract address must be independently re-verified against Circle's/Arc's own documentation at deploy time — never copied from this testnet record, even though Arc's testnet USDC happens to sit at a distinctive, memorable address (0x3600...0000).
- Arc's public mainnet launches 2026-09-16 — see packages/contracts/script/DeployArcMainnet.s.sol, prepared but not run, with its chain-id guard deliberately left as an env-var placeholder rather than a guessed constant.
Base Sepolia
Chain ID 84532. Deployed 2026-08-18 from commit 7b1d6ed.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Touchstone: common questions
- Is Touchstone MCP server safe?
- Mostly: it is graded B (80/100). Read the Touchstone safety report
- How do I install Touchstone?
- It runs remotely at mcp.touchstoneassay.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Touchstone need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Touchstone maintained?
- The last commit was 8 days ago (2026-10-29). The latest release is v0.1.0.
- Is Touchstone up?
- 96% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Touchstone compare with other MCP servers?
- safety score 80/100 (higher than 60% of 48,243 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.