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

⚡ 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

tobyrichmond12-max

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
🚨
Reads files from sensitive locations
Touches: google_credentials.json, config/google_credentials.json
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — system_status (line 158: result = subprocess.run(["free", "-h"], capture_output=True, text=True))
🔐
You'll be asked for 8 credentials: TELEGRAM_BOT_TOKEN, VAPID_PUBLIC_KEY, CANVAS_API_TOKEN, GOOGLE_MAPS_API_KEY, TODOIST_API_KEY, ANTHROPIC_API_KEY, TODOIST_API_TOKEN, ELEVENLABS_API_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.
configALFRED_WHISPER_MODEL
🔐 secretTELEGRAM_BOT_TOKEN
🔐 secretVAPID_PUBLIC_KEY
configSEARXNG_URL
configHTTPS_PROXY
confighttps_proxy
🔐 secretCANVAS_API_TOKEN
configCODEX_BIN
configCLAUDE_BIN
configCODEX_RUN_TIMEOUT
🔐 secretGOOGLE_MAPS_API_KEY
🔐 secretTODOIST_API_KEY
configGOOGLE_CALENDAR_CREDS
configOLLAMA_URL
configOLLAMA_EMBED_MODEL
configNTFY_URL
configNTFY_TOPIC
configVAPID_CONTACT
🔐 secretANTHROPIC_API_KEY
configALFRED_VISION_MODEL
configLAPTOP_MCP_URL
🔐 secretTODOIST_API_TOKEN
🔐 secretELEVENLABS_API_KEY
configALFRED_VOICE_ID
// 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

6/6 tools missing one or more hints — query_vault (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); run_local_inference (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); store_observation (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 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.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — system_status (line 158: result = subprocess.run(["free", "-h"], capture_output=True, text=True))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool inputs are validated

5/6 tool handlers declare input schemas (83%)

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

Tool handlers catch errors

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

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.).

Tests exist

No test files found

Add tests that exercise each declared tool.

No access to sensitive paths

Reads sensitive paths: google_credentials.json, config/google_credentials.json

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

Tool description accuracy

system_status: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

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/tobyrichmond12-max-alfred-q672n9?variant=verified)](https://m8ven.ai/mcp/tobyrichmond12-max-alfred-q672n9)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 5fff321c02de4fc8b276dc4b13011d94bf67cced
code hash: 0824e38ade49f26a3f7740e23d9901a566f70813e5ef04abc501a9e269eacf52
verified: 8/8/2026, 7:59:13 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