ctxmesh (ctxmesh/ctxmesh) is an MCP server listed on the M8ven Trust Index. It scores 67 out of 100, grade C. It declares 7 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Limited view
67/100

ctxmesh

Kubernetes-native control plane for deploying, governing, and observing AI agents — CRDs, guardrails, approvals, evals, canary rollouts, and end-to-end tracing.

→ ctxmesh/ctxmesh· listed on github_repo_search

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Go is partially covered.

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

ctxmesh

Source: github_repo_search

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

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
✅
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.
// tools this server exposes7 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.

delegate_to
handoff_to
knowledge_search
dynamic_tool_160
dynamic_tool_220
dynamic_tool_276
dynamic_tool_358
// 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.
configAGENT_NAME
configAGENT_PORT
configCTXMESH_DELEGATE_BLOCKING
configDELEGATE_ENABLED
configDELEGATE_ROSTER
configKNOWLEDGE_BASES
configKNOWLEDGE_BASE_ENABLED
configSKILL_REFS
configVISUAL_LABEL
configVISUAL_MODE
configVISUAL_PORT
configOUT_DIR
configOTEL_EXPORTER_OTLP_ENDPOINT
configAGENT_VERSION
configAGENT_RUNTIME
configMAX_STEPS
configMODEL_ROUTE
configSYSTEM_PROMPT
configPROMPT_FILE
configGUARDRAIL_POLICY
// 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

7/7 tools missing one or more hints — delegate_to (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); handoff_to (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); knowledge_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 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 inputs are validated

Only 0/3 tool handlers declare input schemas (0%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

2/3 tool handlers wrap calls in try/catch (67%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

3/7 tools referenced in tests (43%)

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 5 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/ctxmesh/ctxmesh)](https://m8ven.ai/mcp/ctxmesh/ctxmesh)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 15ec65d2bae4c43fb15d94d43fbcac485d72d868
code hash: e3e004c920e396cc13965a284af799f7a5c3c5defb18fd7d137659359b60eac8
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