Security review

Is jcodemunch-mcp MCP safe to give an agent?

destructive capableneeds cautiondestructive capablehealthy

A factual risk summary built from jcodemunch-mcp’s real tool surface, execution model, and verification history — not a vibe. Trust score 46/100.

01What it can do

Has tools that can delete or irreversibly change data.

92 tools observeddestructive presentwrite present

02Execution model

Runs locally over stdio — the server process executes on your machine with your user's privileges. Vet the source and package before granting access.

Installs via uvx (`uvx jcodemunch-mcp`) — it pulls and executes third-party code; pin versions and review the source.

03Permissions & auth

Query a database · writeManage GitHub · destructiveVector & semantic search · writeVersion control (git) · writeFetch a URL · writeMaps & location · write

The write/destructive access this server can exercise, inferred from its verified tools.

04Verification

handshakepassed — tool surface is real

runshandshake:failed · metadata:passed · tools_list:passed · handshake:passed · metadata:passed · metadata:passed · metadata:passed · metadata:passed · tools_list:passed · handshake:passed

last_checked2026-08-16 22:36Z

sourcesGitHub repo search [p4]

Reduce the risk

Worried about handing an agent raw access? See governed agents in action — Apex gives your AI paced, capped, fully-logged hands with approval queues before anything runs.

Explore Apex →

See also: full server page · setup · alternatives