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

Trusted

72/100

inspector

Item: inspector
Rating: 72
Author: M8ven

Testing and evaluation platform to chat, inspect, and debug MCP servers, MCP apps, and ChatGPT apps.

→ 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 push why connect →

Who stands behind it

MCPJam

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

npmscored separately 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

⚠️

Known vulnerabilities in dependencies: 3 high

Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.

✅

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 2 credentials: DISCORD_SERVICE_TOKEN, MCPJAM_HOST_TOOL_RELAY_CREDENTIAL

These are read from process.env at runtime. Make sure you trust where they’ll be sent.

// known CVEs in dependencies3 high1 medium3 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

highpostcss@8.4.31GHSA-6g55-p6wh-862q

PostCSS: Arbitrary file read and information disclosure via attacker-controlled sourceMappingURL in CSS comments

highpostcss@8.4.31GHSA-r28c-9q8g-f849

PostCSS: Path Traversal in Previous Source Map Auto-Loading (sourceMappingURL) leads to Arbitrary .map File Disclosure

highsharp@0.35.2GHSA-rgj7-g3m4-5g8c

sharp: Vulnerabilities in libheif: GHSA-g89c-p67h-r497 and GHSA-2jg2-4ch7-h545

mediumpostcss@8.4.31GHSA-fxqj-rqcc-2cmp

PostCSS: incomplete fix of GHSA-6g55-p6wh-862q — attacker-controlled sourceMappingURL reads arbitrary .map files when `from` is unset

low@hono/node-server@1.19.14GHSA-frvp-7c67-39w9

Node.js Adapter for Hono: Path traversal in `serve-static` on Windows via encoded backslash (`%5C`)

Depend on this server? Get alerted when its CVEs change.Watch this server free →

// 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.

configCONVEX_HTTP_URL

🔐 secretDISCORD_SERVICE_TOKEN

configDISPLAY

configDOCKER_CONTAINER

configELECTRON_APP

configELECTRON_RESOURCES_PATH

configIS_PACKAGED

configMCPJAM_AGENT_PLATFORM_TOOLS

configMCPJAM_DOCS_MCP_URL

configMCPJAM_FORCE_ELECTRON_OAUTH_FALLBACK

configMCPJAM_HOST_TOOL_LOG

🔐 secretMCPJAM_HOST_TOOL_RELAY_CREDENTIAL

configMCPJAM_HOST_TOOL_RELAY_URL

configMCPJAM_INSPECTOR_PARENT_PID

configMCPJAM_PLATFORM_MCP_URL

configMCPJAM_RUNTIME_ROOT

configMCPJAM_SPEC_MCP_URL

configMCP_AUTO_CONNECT_SERVER

configMCP_CONFIG_DATA

configMCP_CSP_MODE

configMCP_INITIAL_TAB

configMCP_SERVER_ARGS

configMCP_SERVER_COMMAND

configOPENAI_BASE_URL

configSERVER_PORT

Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.

deployPORT

// quality suggestions

Dependencies

108 runtime dependencies (51 dev), 1 flagged: playwright

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

2/2 tools missing one or more hints — echo (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); regional-echo (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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

1/2 tools referenced in tests (50%)

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

Production dependencies are patched

0 critical, 2 high severity in production deps — postcss@8.4.31 (high), postcss@8.4.31 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Dependency freshness

7/108 production deps abandoned (no release in 2+ years): proper-lockfile@2022-06-24 (4.2y), fast-deep-equal@2023-06-22 (3.2y), gray-matter@2023-07-12 (3.2y)

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/mcpjam/inspector)](https://m8ven.ai/mcp/mcpjam/inspector)

Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.

commit: 06962479eec5e28899adb8f37d541d31432ddb2c

code hash: 1bfda0ee28cde681e29ce92ac448a5485982c79724267287256829ee44c44996

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