touchstone-mcp (Touchstone-CV/touchstone-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 4 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

touchstone-mcp

Local MCP server that signs and records agent actions into a tamper-evident log using Ed25519 keys for frictionless integration with Touchstone.

→ Touchstone-CV/touchstone-mcp· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

Touchstone-CV

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
2 flows detected: TOUCHSTONE_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 2 credentials: TOUCHSTONE_API_KEY, TOUCHSTONE_SIGNING_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes4 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

touchstone_record

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

touchstone_recorder_info

Your recorder: id, subject, trust tier, head sequence.

touchstone_disclose

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

touchstone_verify

Independently verify a disclosure (token or bundle).

// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretTOUCHSTONE_API_KEY"": "tsk_...",
configTOUCHSTONE_BASE_URLno Defaults to https://touchstone.cv
configTOUCHSTONE_KEY_FILEalt Path to JSON {"seed_b64":"…"} instead of the inline seed
configTOUCHSTONE_RECORDER"": "rec_...",
🔐 secretTOUCHSTONE_SIGNING_KEY"": "<base64 Ed25519 32-byte seed>"
configTOUCHSTONE_SUBJECT"": "<your-colony-sub>",
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

4/4 tools missing one or more hints — touchstone_record (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); touchstone_recorder_info (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); touchstone_disclose (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +1 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/touchstone-cv/touchstone-mcp)](https://m8ven.ai/mcp/touchstone-cv/touchstone-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 9fbffdab64de9a5575ec4a3df3724b4ec5e7a16b
code hash: 007f4f648b48bb8fa3e8cb6ab45d357a305e0f4f80c07480458d9497919bbe8c
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client