F
Warning
32/100
1 day ago

simple-mcp

A local Model Context Protocol (MCP) server with a React admin panel for managing integrations (Jira, GitHub), AI-powered agents, and server configuration.

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we 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

heshansw

Source: github_code

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 →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
⚠️
Tool descriptions don’t match what handlers do
2 tools describe read intent but their handlers mutate — code_health_snapshot (line 49: execSync("git rev-parse HEAD", { cwd: directoryPath, encoding: "utf-8" })); code_health_type_coverage (line 50: anyPattern.exec(stripped))
🚨
Known vulnerabilities in dependencies: 1 critical, 4 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
// known CVEs in dependencies1 critical4 high3 medium22 low

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

criticalvitest@3.2.4GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

highdrizzle-orm@0.39.3GHSA-gpj5-g38j-94v9

Drizzle ORM has SQL injection via improperly escaped SQL identifiers

highhono@4.12.8GHSA-88fw-hqm2-52qc

hono: CORS Middleware reflects any Origin with credentials when `origin` defaults to the wildcard

highvite@6.4.1GHSA-fx2h-pf6j-xcff

vite: `server.fs.deny` bypass on Windows alternate paths

highvite@6.4.1GHSA-p9ff-h696-f583

Vite Vulnerable to Arbitrary File Read via Vite Dev Server WebSocket

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.
configCLAUDE_MCP_DB_PATH~/.simple-mcp/data.db
configWHISPER_BIN_PATHNo auto-detect Path to whisper-cpp binary (local mode only)
configWHISPER_MODELTo use a different model (e.g., large-v3 for best accuracy), set =large-v3 in .env before running pnpm setup:audio.
configWHISPER_MODELS_DIRNo ~/.simple-mcp/models/ Directory for Whisper model files
// quality suggestions

Tool annotations

3/74 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

71/74 tools missing one or more hints — audio_check_prerequisites (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); audio_get_transcript (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); audio_get_meeting_summary (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +68 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.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — code_health_duplication deletes at line 161 (rm(tmpDir, { recursive: true, force: true }))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Descriptions match behaviour

2 tools describe read intent but their handlers mutate — code_health_snapshot (line 49: execSync("git rev-parse HEAD", { cwd: directoryPath, encoding: "utf-8" })); code_health_type_coverage (line 50: anyPattern.exec(stripped))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool inputs are validated

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

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

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 8/74 tools referenced in tests (11%)

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 — drizzle-orm@0.39.3 (high), hono@4.12.8 (high)

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

Dev dependencies

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

Upgrade dev dependencies when convenient.

Dependency freshness

1/17 production deps stale: typhonjs-escomplex@2022-06-28 (4.1y)

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 9 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 Verified](https://m8ven.ai/badge/mcp/heshansw-simple-mcp-1sz480?variant=verified)](https://m8ven.ai/mcp/heshansw-simple-mcp-1sz480)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: cddcb67f4e6b2af81c3d0e5ff9d2ef9b98d5a5ee
code hash: be668868d6b18de5de4de70ea6f922e1152687e238747f6059dfee61767bcd79
verified: 8/18/2026, 9:56:12 AM
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