C
Limited view
65/100
11 days ago

elspeth

Auditable Sense/Decide/Act pipelines for high-stakes data processing.

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

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

johnm-dta

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 6 credentials: ELSPETH_EVAL_API_KEY, OPENROUTER_API_KEY, ANTHROPIC_API_KEY, GH_TOKEN, GITHUB_TOKEN, ELSPETH_WEB__SECRET_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.
configOIDC_TLS_SPKI_SHA256
configPLAYWRIGHT_BACKEND_BASE_URL
configPLAYWRIGHT_BACKEND_PORT
configPLAYWRIGHT_E2E_DATA_DIR
configPLAYWRIGHT_E2E_RUN_ID
configPLAYWRIGHT_FRONTEND_BASE_URL
configPLAYWRIGHT_FRONTEND_PORT
configPLAYWRIGHT_HEADLESS
configSTAGING_BASE_URL
configSTAGING_IGNORE_HTTPS
configTUTORIAL_DIAGNOSTIC_QUESTION
configTUTORIAL_EXPECT_VAGUE_TERM
configTUTORIAL_PROMPT_OVERRIDE
configELSPETH_DATABASE_URL
configWEB_CONCURRENCY
configELSPETH_EVAL_BASE_URL
🔐 secretELSPETH_EVAL_API_KEY
🔐 secretOPENROUTER_API_KEYexport ="sk-or-..."
🔐 secretANTHROPIC_API_KEY
🔐 secretGH_TOKEN
🔐 secretGITHUB_TOKEN
🔐 secretELSPETH_WEB__SECRET_KEYexport ="local-dev-secret-key"
configGIT_COMMIT_SHA
configELSPETH_WEB__HOST
configELSPETH_WEB__PORT
configELSPETH_WEB__AUTH_PROVIDER
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
// quality suggestions

Dependencies

2 dependencies, 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

7/7 tools missing one or more hints — call_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); dynamic_tool_629 (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); dynamic_tool_687 (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 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

2/3 tool handlers wrap calls in try/catch (67%)

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

Tool test coverage

Only 0/7 tools referenced in tests (0%)

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

No eval / new Function

1 eval() or new Function() call — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

Shell command execution

22 child_process calls — 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/johnm-dta-elspeth-a4txyo)](https://m8ven.ai/mcp/johnm-dta-elspeth-a4txyo)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 720d441336434d227c2a00caaac100db48a07d5c
code hash: df0d30939082b054f08d021aae258e4c651fd26017a8df49e338a8f90fd71ee6
verified: 8/8/2026, 8:48:20 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