A stdio MCP server providing AI agents with a stable tool interface to read and write TCM test cases through REST, including search, CRUD operations, and a dry-run-to-commit safety flow.
Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
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
JoinFullStackDev
Source: Glama
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 →
Install from
M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default
Zod denial of service vulnerability
CLUTCH_API_KEYThe server resolves its mode at startup. Precedence: → login session file → TCM_USER_TOKEN.MCP_AGENT_USER_IDClutch key (headless) CLUTCH_API_KEY X-Clutch-Key Torque via Clutch/OpenClaw The service profile — seeSUPABASE_ANON_KEYAnon key capture: the helper sniffs the public apikey header from Supabase network traffic. If capture ever fails, set (safe to expose) and re-run.TCM_BASE_URLno (defaults to production) all Base URL of the TCM instance. Defaults to https://tcm-ochre.vercel.app; set only to point at a preview / self-hosted instance.TCM_BROWSER_PROFILEBrowser profile: ~/.tcm-mcp/browser, override with .TCM_SESSION_FILESession file location: ~/.tcm-mcp/session.json, override with .TCM_USER_TOKEN"env": { "": "${TCM_USER_TOKEN}" },NEXT_PUBLIC_SUPABASE_ANON_KEYTool 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 — search_suite (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_test_cases (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_test_case (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.
License file
No license file
Add a LICENSE file (MIT, Apache-2.0, etc.).
Tests exist
No test files found
Add tests that exercise each declared tool.
Production dependencies are patched
0 critical, 1 high severity in production deps — @modelcontextprotocol/sdk@1.0.0 (high), zod@3.22.0 (low)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
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.
[](https://m8ven.ai/mcp/joinfullstackdev-tcm-mcp-srkyl3)?variant=verified from the URL.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