Back to MCP Trust Indexm8ven
A
Trusted
98/100
2 months ago

MCPJam/inspector

MCP server unit testing, end to end (e2e) testing, and server evals

→ MCPJam/inspector· npm: @mcpjam/sdk· listed on npm

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

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

MCPJam

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

npmGitHub

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: ANTHROPIC_API_KEY, ASANA_TOKEN, BRIGHTDATA_API_TOKEN, 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.
🔐 secretANTHROPIC_API_KEY
🔐 secretASANA_TOKEN
configAUTHKIT_DOMAIN
🔐 secretBRIGHTDATA_API_TOKEN
configINPUT
configMCPJAM_AUTH_FILE
configMCPJAM_CLI_DISABLE_BROWSER_OPEN
configMCPJAM_INSPECTOR_URL
🔐 secretOPENAI_API_KEY
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
deploySUPABASE_SERVICE_ROLE_KEY
deploySUPABASE_URL
// 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 — orderCoffee (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); drinkCoffee (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_status (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 inputs are validated

Only 2/6 tool handlers declare input schemas (33%)

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

Tool handlers catch errors

Only 0/6 tool handlers wrap calls in try/catch (0%)

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

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.

Shell command execution

1 child_process call — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

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 6 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/mcpjam-sdk-q8ucef)](https://m8ven.ai/mcp/mcpjam-sdk-q8ucef)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: e69da62fcb6af9ce540f44c2aed563796cbec5c0
code hash: 6afc02f2001ca93a052a28a55f0979a0e66958ebef5e8ebdf1012eb0e191a5d2
verified: 6/11/2026, 12:17:25 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