joern-mcp-server (effortlessdevsec/joern-mcp-server) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

C
Emerging
74/100
17 days ago

joern-mcp-server

Joern Advanced MCP Server MCP (Model Context Protocol) server that exposes **Joern** code analysis as tools: import code, query dataflows, list methods, dump AST/CFG/PDG, and run scans.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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

effortlessdevsec

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
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: JOERN_SERVER_BASIC_PASS, JOERN_SERVER_PASSWORD
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.
configJOERN_HOMEJoern Installed; should point at the install (contains joern-cli/) for spawn paths
configJOERN_MCP_DEBUGVerbose debugging — =1 logs routing, HTTP timing, and spawn argv on stderr only
configJOERN_MCP_DEBUG_QUERY_MAXMax chars of query in debug previews (default 2000)
configJOERN_MCP_FORCE_SPAWNForce joern --script even if URL is set
configJOERN_MCP_HTTP_ONLYStrict HTTP mode — =1 blocks spawn for scripts; CLI-only tools error (see [BACKEND.md](./BACKEND.md))
🔐 secretJOERN_SERVER_BASIC_PASS
configJOERN_SERVER_BASIC_USER
🔐 secretJOERN_SERVER_PASSWORDJOERN_SERVER_USER / Basic auth for HTTP (see BACKEND for aliases)
configJOERN_SERVER_TIMEOUT_MS/query-sync timeout (default 300000)
configJOERN_SERVER_URLHTTP-first — With , script tools send CPGQL in memory to /query-sync (no joern --script subprocess per call)
configJOERN_SERVER_USER/ JOERN_SERVER_PASSWORD Basic auth for HTTP (see BACKEND for aliases)
// 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

18/18 tools missing one or more hints — joern_dump_graphs (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); joern_export (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); joern_find_calls (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +15 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 handlers catch errors

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

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

Tests exist

No test files found

Add tests that exercise each declared tool.

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 4 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/effortlessdevsec-joern-mcp-server-14m1yr)](https://m8ven.ai/mcp/effortlessdevsec-joern-mcp-server-14m1yr)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 17edcb555dca6c50c3df59f81d22390b63f383cf
code hash: 400dd6d1dee766ba98597e919fb7b3c9ae468f2bc323e37bea03ca26c42be18c
verified: 8/8/2026, 7:42:30 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