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

NehoraiHadad

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
🚨
Secret credentials may flow to a network call
2 flows detected: NEXT_PUBLIC_VAPID_PUBLIC_KEY. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 2 critical, 14 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 4 credentials: JWT_SECRET, TERMINAL_JWT_SECRET, VAPID_PRIVATE_KEY, VAPID_PUBLIC_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 critical14 high9 medium8 low

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

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

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

criticalvitest@3GHSA-9crc-q9x8-hgqq

Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening

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

Drizzle ORM has SQL injection via improperly escaped SQL identifiers

highnext@16.1.6GHSA-267c-6grr-h53f

Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes

highnext@16.1.6GHSA-26hh-7cqf-hhc6

Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Up

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.
configAGENDO_AGENT_ID
configAGENDO_PROJECT_ID
configAGENDO_SESSION_ID
configAGENDO_TASK_ID
configAGENDO_URL
configALLOWED_WORKING_DIRS
configHEARTBEAT_INTERVAL_MS
🔐 secretJWT_SECRETYes Min 16 chars (auto-generated by setup script)
configLOG_DIRNo Session log directory (default: ./logs)
configLOG_LEVEL
configMCP_SERVER_PATH
configSTALE_JOB_THRESHOLD_MS
🔐 secretTERMINAL_JWT_SECRET
configTERMINAL_PORT
🔐 secretVAPID_PRIVATE_KEY
🔐 secretVAPID_PUBLIC_KEY
configVAPID_SUBJECT
configWORKER_HTTP_PORT
configWORKER_ID
configWORKER_MAX_CONCURRENT_JOBS
configWORKER_POLL_INTERVAL_MS
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployNEXT_PUBLIC_APP_VERSION
deployNEXT_PUBLIC_GIT_SHA
deployNEXT_PUBLIC_URL
deployNEXT_PUBLIC_VAPID_PUBLIC_KEY
deployPORT
// quality suggestions

All four hints declared on every tool

24/24 tools missing one or more hints — brainstorm_signal (missing: openWorldHint); brainstorm_get_state (missing: openWorldHint); save_plan (missing: openWorldHint), +21 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 inputs are validated

19/24 tool handlers declare input schemas (79%)

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

Tool handlers catch errors

Only 0/24 tool handlers wrap calls in try/catch (0%)

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

License file

No license file

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

Tool test coverage

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

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

Shell command execution

3 child_process calls — runs shell commands

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

Secrets stay with their owner

2 secret/sensitive values flow into network calls (NEXT_PUBLIC_VAPID_PUBLIC_KEY → /api/notifications/subscribe, NEXT_PUBLIC_VAPID_PUBLIC_KEY → /api/notifications/subscribe)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Production dependencies are patched

0 critical, 14 high severity in production deps — drizzle-orm@0.44 (high), next@16.1.6 (high)

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

Dev dependencies

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

Upgrade dev dependencies when convenient.

Dependency freshness

3/47 production deps abandoned (no release in 2+ years): ansi-to-html@2022-06-13 (4.2y), @dnd-kit/utilities@2023-11-06 (2.8y), web-push@2024-01-16 (2.6y)

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/nehoraihadad-agendo-19vjzm?variant=verified)](https://m8ven.ai/mcp/nehoraihadad-agendo-19vjzm)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 1cc5c08c3b86e2076422e7155f3b24cf1c53e114
code hash: c303eceb1aa41acd3b9a717f9806c6d165360e992493b2c55c1e1c8b55cbc914
verified: 8/8/2026, 7:41:48 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