Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Touchstone

NPM · @TOUCHSTONE-CV/MCP · 2 COMPONENTS · SCANNED AUG 3

Bitcoin-anchored, tamper-evident audit log for AI agents — record, disclose and verify actions.

−8 this week 79 Trust /100
Trust breakdown (6 categories)

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 →

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 23 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
  • 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 Management27
  • Stability observed for 8 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @touchstone-cv/mcp

# add to Claude Code
claude mcp add cv-touchstone-touchstone -- npx -y @touchstone-cv/mcp
# add to Codex CLI
codex mcp add cv-touchstone-touchstone -- npx -y @touchstone-cv/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cv-touchstone-touchstone": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@touchstone-cv/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cv-touchstone-touchstone --command npx --arg -y --arg @touchstone-cv/mcp
# ~/.hermes/config.yaml
mcp_servers:
  cv-touchstone-touchstone:
    command: "npx"
    args: ["-y", "@touchstone-cv/mcp"]
// mcp.json
{
  "mcpServers": {
    "cv-touchstone-touchstone": {
      "command": "npx",
      "args": [
        "-y",
        "@touchstone-cv/mcp"
      ]
    }
  }
}
Changelog

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.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Aug 26 +18
    • Malware scan: unverified → pass security
    • Stability: unverified → 0.23 functional
  • 1 Aug 26 −9
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 87

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Analysed npm/@touchstone-cv/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

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
Discovery method:
attestation_endpoint
Dependencies 0 packages

0 packages in the resolved dependency tree.

MCP tools — 4 exposed · ~254 tokens

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.

Tool Tokens
touchstone_disclose ~58

Create a shareable, independently-verifiable disclosure of selected entries.

NameTypeReqDescription
revealobjectoptional selective-disclosure map {seq: [field keys to reveal]}; unlisted fields stay withheld
seqsarrayyes

No output schema declared.

No examples provided.

touchstone_record ~139

Sign (locally, key never leaves this machine) and append an event to your recorder.

NameTypeReqDescription
client_tsstringoptional ISO-8601 UTC
counterparty_substringoptional: the other party's Colony sub
event_typestringyese.g. tool_call, decision, commitment
payloadobjectyesarbitrary JSON describing what happened
selective_disclosurebooleancommit each field separately (salted Merkle root) so a later disclosure can reveal a subset of fields and withhold the rest
store_payloadbooleandefault 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).

NameTypeReqDescription
bundleobject
tokenstring

No output schema declared.

No examples provided.