Back to MCP Trust Indexm8ven
C
Warning
74/100
9 hours ago

Front-AI-review

→ CFMjayb/Front-AI-review· listed on github_code

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

CFMjayb

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 →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: EMAIL_MCP_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 4 credentials: MCP_API_KEY, FRONT_API_TOKEN, ANTHROPIC_API_KEY, EMAIL_MCP_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.
🔐 secretMCP_API_KEY
configTRANSPORT
configLEDGER_BACKEND
configGCP_PROJECT
configUSE_SECRET_MANAGER
🔐 secretFRONT_API_TOKENfill in and ANTHROPIC_API_KEY
🔐 secretANTHROPIC_API_KEYfill in FRONT_API_TOKEN and
configLOG_LEVEL
configCOS_TIMEZONE
configCOS_ADMIN_EMAIL
configCOS_SALLY_EMAIL
configINBOX_IDScode — just add the inbox to ). See docs/chief-of-staff/INGESTION.md.
configTEAMMATE_IDS
configANTHROPIC_MODEL
configANTHROPIC_MODEL_FAST
configPLAUD_ENABLED
configSOURCE_MAX_PAGES
configDRY_RUN
configEARLIEST_DATE
configLOOKBACK_DAYS
configMAX_RUN_COST_USD
configRUN_INTERVAL_HOURS
configBRIEFING_DELIVERYDelivery goes through the shared sender layer (below); =email
configCOS_CALENDARSAgent sweeps pull your own + named shared calendars () into an
configQUIET_THRESHOLD_HOURS→ i_owe; an outbound ask gone quiet ≥ (default 36) →
configCOS_ENABLED
configCOS_OWNER_EMAILS
configSENDER_TOConfig: SENDER_TRANSPORT (front), , SENDER_FRONT_CHANNEL_ID.
configFIRESTORE_PROJECT
configCOS_DB_PATH
configCOS_OWNER_NAMES
configSENDER_FRONT_CHANNEL_IDConfig: SENDER_TRANSPORT (front), SENDER_TO, .
configEMAIL_MCP_URL
🔐 secretEMAIL_MCP_API_KEY
configSENDER_TRANSPORTConfig: (front), SENDER_TO, SENDER_FRONT_CHANNEL_ID.
configANTHROPIC_MODEL_ANALYZE
configSPAM_PREFILTER
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

28/28 tools missing one or more hints — front_list_inboxes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); front_list_channels (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); front_list_teammates (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +25 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.).

Tool test coverage

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

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

Secrets stay with their owner

1 secret/sensitive value flow into network calls (EMAIL_MCP_API_KEY → dynamic)

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

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 5 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/cfmjayb-front-ai-review-1r0tid?variant=verified)](https://m8ven.ai/mcp/cfmjayb-front-ai-review-1r0tid)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 5982ebfc027bd529444335ff5cc166908f582c1d
code hash: 5bb2ede74fa1ece9bb7af8987e49991aeaee8af5f69aef7bd6f3d1b751fc8a53
verified: 8/19/2026, 9:18:53 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