CodeMax
Cross-stack MCP server that scans frontend and backend code together, detects mismatches like phantom calls, dead endpoints, and field drift, and provides a full-stack health audit.
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
rish-e
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
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.
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.
full_stack_auditRun a comprehensive full-stack analysis — scans frontend API calls, backend routes, cross-references contracts, detects mismatches, auth gaps, dead endpoints, and scores overall health. The complete picture.
health_checkQuick full-stack health score with the top 5 issues. Faster than a full audit — use for a pulse check.
check_contractsCompare frontend API calls against backend routes. Find phantom calls (frontend → nowhere), dead endpoints (backend → unused), method mismatches, auth gaps, and field drift.
trace_issueGiven a bug description or error message, determine whether it's a frontend, backend, or cross-stack issue. Traces through the call chain and identifies the root cause.
map_dependenciesMap all connections between frontend components and backend endpoints. Shows which frontend files depend on which API routes, plus orphaned endpoints and phantom calls.
scan_frontendScan frontend code for all API calls, data fetching patterns, environment variable usage, and error handling gaps.
scan_backendScan backend code for all route handlers, middleware, authentication patterns, validation, and error handling.
check_envCross-reference environment variables across .env files, frontend code, and backend code. Find missing vars, public/private prefix issues, and drift between .env.example and .env.
detect_projectAnalyze and report the project structure — frameworks, ORM, monorepo detection, frontend/backend path separation, package manager, and TypeScript usage.
get_historyView the full audit history — health score trend over time, issue lifecycle (new, fixed, regressed), and scan statistics. Shows how the codebase has improved or declined across audits.
log_fixManually log how a specific issue was fixed. The fix description is recorded in the ledger and appears in REPORT.md. Use the issue ID from `get_history` or `full_stack_audit`.
acknowledge_issueMark an issue as acknowledged — you know about it and it's intentional or acceptable. Acknowledged issues still appear in reports but won't be flagged as action items.
get_reportRead the latest generated REPORT.md — the living documentation of all discovered issues, fixes, health trends, and API contract maps. Located at .codemax/REPORT.md.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
When Vitest UI server is listening, arbitrary file can be read and executed
Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse
Anthropic's MCP TypeScript SDK has a ReDoS vulnerability
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default
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
13/13 tools missing one or more hints — full_stack_audit (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); health_check (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); check_contracts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +10 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/13 tools referenced in tests (0%)
Write tests that reference each tool by name so every tool has at least one test.
Shell command execution
14 child_process calls — runs shell commands
Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.
Production dependencies are patched
0 critical, 4 high severity in production deps — @modelcontextprotocol/sdk@1.12.1 (high), @modelcontextprotocol/sdk@1.12.1 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
Dev dependencies
2 critical/high in dev-only deps (does not ship to users)
Upgrade dev dependencies when convenient.
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/rish-e/codemax)?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