OpenRath (Rath-Team/OpenRath) is an MCP server listed on the M8ven Trust Index. It scores 98 out of 100, grade A. It declares 6 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
A
Trusted
98/100
8 days ago

OpenRath

An open-source, PyTorch-like runtime for dynamic multi-agent and multi-session workflows.

→ Rath-Team/OpenRath· listed on github_topic

Trusted. Deep verification, no outstanding findings, and an established reputation. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we 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

Rath-Team

Source: github_topic

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

GitHub

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 4 credentials: OPENRATH_TOKEN, OPEN_VIKING_EMBEDDING_API_KEY, OPEN_VIKING_VLM_API_KEY, OPENAI_API_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.
🔐 secretOPENRATH_TOKEN
configOPENRATH_TENANT_ID
configOPENRATH_GRANTS
configOPENRATH_DB_SCHEMA
configOPENRATH_DB_POOL_MAX_SIZE
configOPENRATH_EMBEDDED_WORKER
configHOSTNAME
configOPENRATH_WORKER_LEASE_SECONDS
configOPENRATH_REVISION_ID
🔐 secretOPEN_VIKING_EMBEDDING_API_KEY
🔐 secretOPEN_VIKING_VLM_API_KEY
configOPEN_VIKING_EMBEDDING_API_BASE
configOPEN_VIKING_VLM_API_BASE
configOPEN_VIKING_EMBEDDING_MODEL
configOPEN_VIKING_EMBEDDING_DIMENSION
configOPEN_VIKING_VLM_MODEL
🔐 secretOPENAI_API_KEY
configOPENAI_BASE_URL
configOPENAI_DEFAULT_MODEL
configOPENRATH_APP
configOPENRATH_HOST
configOPENRATH_PORT
configOPENRATH_WEB_WORKERS
configOPENRATH_WORKER_ID
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployOPENRATH_POSTGRES_DSN
// 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

6/6 tools missing one or more hints — backendtoolcommandrun (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); backendtoolfilesread (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); backendtoolfileswrite (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 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.

Tool test coverage

Only 0/6 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

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/rath-team/openrath)](https://m8ven.ai/mcp/rath-team/openrath)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 82819467b001896c8b22f98ba99f1634c78b0cfc
code hash: 7a5fb8f0a5b5f4a31641dc085b61d31a7629e65d8fec50df0b3e07503e81d5c5
verified: 9/3/2026, 4:46:43 AM
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