Touchstone
NPM · @TOUCHSTONE-CV/MCP · 2 COMPONENTS · SCANNED SEP 20
Bitcoin-anchored, tamper-evident audit log for AI agents — record, disclose and verify actions.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Touchstone-CV/touchstone-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 71 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 291 tokens (~72/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Touchstone MCP server?
Touchstone runs locally as an npm package, launched with npx -y @touchstone-cv/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @touchstone-cv/mcp
claude mcp add cv-touchstone-touchstone -- npx -y @touchstone-cv/mcp
{
"mcpServers": {
"cv-touchstone-touchstone": {
"command": "npx",
"args": [
"-y",
"@touchstone-cv/mcp"
]
}
}
} {
"servers": {
"cv-touchstone-touchstone": {
"command": "npx",
"args": [
"-y",
"@touchstone-cv/mcp"
]
}
}
} codex mcp add cv-touchstone-touchstone -- npx -y @touchstone-cv/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cv-touchstone-touchstone": {
"type": "local",
"command": [
"npx",
"-y",
"@touchstone-cv/mcp"
],
"enabled": true
}
}
} openclaw mcp add cv-touchstone-touchstone --command npx --arg -y --arg @touchstone-cv/mcp
mcp_servers:
cv-touchstone-touchstone:
command: "npx"
args: ["-y", "@touchstone-cv/mcp"] {
"McpServers": {
"cv-touchstone-touchstone": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@touchstone-cv/mcp"
]
}
}
} assistant mcp add cv-touchstone-touchstone -t stdio -c npx -a -y @touchstone-cv/mcp
{
"mcpServers": {
"cv-touchstone-touchstone": {
"command": "npx",
"args": [
"-y",
"@touchstone-cv/mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 −3
- Stability: pass → 0.80 functional
- 14 Sept 26 0
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −2
- Stability: pass → 0.83 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@touchstone-cv/mcp@0.3.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Touchstone-CV/touchstone-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Touchstone-CV/touchstone-mcp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 2137182884 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:562906fbd1fb5b20e08017ab14e0676348d02624cde4b435ebb4dd18f6c3bb9a11efb6e5a5b0dfbd6b12207f0445269624854701fda2fc9b6f75ed095 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
touchstone_disclose ~58
Create a shareable, independently-verifiable disclosure of selected entries.
| Name | Type | Req | Description |
|---|---|---|---|
| reveal | object | – | optional selective-disclosure map {seq: [field keys to reveal]}; unlisted fields stay withheld |
| seqs | array | yes | – |
No output schema declared.
No examples provided.
touchstone_record ~139
Sign (locally, key never leaves this machine) and append an event to your recorder.
| Name | Type | Req | Description |
|---|---|---|---|
| client_ts | string | – | optional ISO-8601 UTC |
| counterparty_sub | string | – | optional: the other party's Colony sub |
| event_type | string | yes | e.g. tool_call, decision, commitment |
| payload | object | yes | arbitrary JSON describing what happened |
| selective_disclosure | boolean | – | commit each field separately (salted Merkle root) so a later disclosure can reveal a subset of fields and withhold the rest |
| store_payload | boolean | – | default true; false keeps only the hash |
No output schema declared.
No examples provided.
touchstone_recorder_info ~24
Your recorder: id, subject, trust tier, head sequence.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
touchstone_verify ~33
Independently verify a disclosure (token or bundle).
| Name | Type | Req | Description |
|---|---|---|---|
| bundle | object | – | – |
| token | string | – | – |
No output schema declared.
No examples provided.
What is the Touchstone MCP server?
Touchstone is an MCP server listed in the public MCP registry as cv.touchstone/touchstone. Bitcoin-anchored, tamper-evident audit log for AI agents, record, disclose and verify actions. This page covers its npm package (@touchstone-cv/mcp).
Is the Touchstone MCP server safe to use?
Touchstone scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Touchstone MCP server expose?
Touchstone exposes 4 tools: touchstone_record, touchstone_recorder_info, touchstone_disclose, touchstone_verify. Their descriptions and schemas cost roughly 254 tokens of context every time the server is loaded.
Is the Touchstone MCP server still maintained?
Touchstone is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Touchstone MCP server under?
Touchstone declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.