roam-code (Cranot/roam-code) is an MCP server listed on the M8ven Trust Index. It scores 89 out of 100, grade B. It declares 246 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
B
Emerging
89/100
8 days ago

roam-code

Local codebase intelligence CLI + MCP server for AI coding agents: SQLite code graph, 28 languages, 287 commands, 246 MCP tools, change-safety gates, audit evidence, zero API keys.

→ Cranot/roam-code· listed on github_topic

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

Cranot

Source: github_topic · also listed on 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

GitHubGlamanot 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: GITHUB_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 2 credentials: GITHUB_TOKEN, KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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.
configROAM_MCP_PRESETcore — a consumer wants a tight prompt surface. This repo's own
configROAM_MCP_LITE
configROAM_MCP_HANDLE_TTL_HOURS
configROAM_MCP_HANDLE_MAX_BYTES
configROAM_MCP_HANDLE_KB
configROAM_RUN_ID
configROAM_MCP_CLIENT_ID
configROAM_AGENT_ID
configROAM_MODE_ENFORCEMENT
configROAM_MODE_DRY_RUNEgress secret-redaction at the MCP wrapper boundary, 4-mode policy_decision enforcement with shadow-mode (), HMAC-linked McpDecisionReceipt + receipt_integrity verdict on roam runs verify.
configROAM_AI_DISABLED
configROAM_AI_ENABLED
configROAM_MCP_HEALTH_FULL
configROAM_MCP_WATCH
configROAM_MCP_LIMITS
configROAM_MCP_DISABLE_COLD_START_GUARD
configROAM_REPO_ROOT
configGITHUB_REPOSITORY
configROAM_DB_DIR
configPYTHONIOENCODING
configROAM_DEBUG
configROAM_CI
configROAM_CONFIG
🔐 secretGITHUB_TOKEN
configROAM_VERBOSE
configROAM_TREE_SITTER_CACHE_DIR
configROAM_TREE_SITTER_CACHE_SEALED
configROAM_TELEMETRY_LOCAL
🔐 secretKEY
configROAM_CROSS_LAYER_PAIR_BUDGET
// 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

246/246 tools missing one or more hints — roam_explore (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); roam_prepare_change (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); roam_review_change (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +243 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.

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 2 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/cranot/roam-code)](https://m8ven.ai/mcp/cranot/roam-code)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 5fd7eda8fa2fc0daaad0bedfd2ac70ca34627e51
code hash: ea76da540afbf7b8c9952eefb4d0669832ecec2bd91d6d638c12aa66963ee723
verified: 9/3/2026, 2:32:57 PM
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