F
Warning
32/100
10 hours ago

claude-agents

Agent Cristian + DAVID automation

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

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

taxicsv70-oss

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
🚨
Hardcoded credentials detected
1 live-looking API key in source: 1 Anthropic API key
🔐
You'll be asked for 5 credentials: API_KEY, ANTHROPIC_API_KEY, CLAUDE_API_KEY, SECRET_KEY, SENDER_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.
configBACKEND_URL
configFLASK_HOST
configFLASK_PORT
configFLASK_ENVdevelopment
configLOG_LEVEL
configREQUEST_TIMEOUT
configMAX_RETRIES
🔐 secretAPI_KEY
configN8N_WEBHOOK_BASE_URL
🔐 secretANTHROPIC_API_KEY
🔐 secretCLAUDE_API_KEY
configCLAUDE_MODEL
configN8N_WEBHOOK_URL
🔐 secretSECRET_KEYyour-secret-key
configSCHEDULER_ENABLED
configSCHEDULER_TIMEZONE
configLOG_FILE
configAPI_TIMEOUT
configSENDER_EMAIL
🔐 secretSENDER_PASSWORD
configSLACK_WEBHOOK_URL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deploySMTP_SERVER
deploySMTP_PORT
// 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

11/11 tools missing one or more hints — create_workflow (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_workflows (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_workflow (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +8 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.

License file

No license file

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

No hardcoded API keys

1 live-looking API key in source: 1 Anthropic API key

Move secrets to environment variables (process.env.X) or your secret manager.

Tool test coverage

Only 3/11 tools referenced in tests (27%)

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

Shell command execution

1 child_process/subprocess call in production code — runs shell commands (backend/core/executor.py:150)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Secrets not logged

2 secret values sent to console.log

Redact or omit secret values from log output.

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 7 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/taxicsv70-oss-claude-agents-18xc4x?variant=verified)](https://m8ven.ai/mcp/taxicsv70-oss-claude-agents-18xc4x)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: f45038ae56b85269adf0479e9b7954b29e6ebb16
code hash: 22d7f8be7f042670ea69e0a1974aed7c790ec599dd6b256e7ffb19cfce5031d8
verified: 8/19/2026, 1:24:22 PM
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