C
Warning
74/100
9 hours ago

platform

BF Agent Platform - Monorepo for BFAgent, Travel Beat, and shared packages

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

achimdehnert

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
1 flow detected: LLM_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 6 credentials: TOKEN, GH_TOKEN, GITHUB_TOKEN, GH_FLEET_TOKEN, LLM_API_KEY, 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.
configEMBED_MODEL
configEMBED_BATCH_SIZE
configGITHUB_OUTPUT
🔐 secretTOKEN
🔐 secretGH_TOKEN
🔐 secretGITHUB_TOKEN
configGITHUB_DIRin ~/.bashrc
🔐 secretGH_FLEET_TOKEN
configOWNER
configGITHUB_STEP_SUMMARY
configREPOS_DIR
configORCHESTRATOR_HEALTH_URL
configGITHUB_REPOSITORY
configREPO_SESSION_DIR
configNAME
configERLAUBT
configGESUNDHEIT
configTUNNEL_NAME
configARTEFAKT_BUDGET_SEIT_OWNER
configARTEFAKT_BUDGET_SEIT_OWNER_PROD
configPYTEST_CURRENT_TEST
configORCHESTRATOR_DB_URL
configALLOW_DEV_DB_FALLBACK
configLESEFLAECHE_FRIST_TAGE
configLESEFLAECHE_ABRUF_STUNDEN
configMAIL_INDEX_CONTAINER
configMAIL_INDEX_SSH
configOLLAMA_HOST
configPRINT_AGENT_ALLOW_EXTERNAL
configDESIGN_HUB_DIR
configPRINT_AGENT_LLM_PRIMARY
configPRINT_AGENT_LLM_FALLBACK
configSHAREDCI_BRANCH
configTODO_BOARD_MAIL_BASIS
configLLM_GATEWAY_URL
configLLM_MODEL
🔐 secretLLM_API_KEY
configPR_NUMBER
configPROJECT_PAT
🔐 secretKEY
configIIL_ADRFW_ADRS_DIR
configX
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployPLATFORM_AUDIT_DSN
// 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

19/19 tools missing one or more hints — search_knowledge (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_document (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_runbook (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +16 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.

Secrets stay with their owner

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

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

Secrets not logged

3 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 4 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/achimdehnert-platform-ylvvjs?variant=verified)](https://m8ven.ai/mcp/achimdehnert-platform-ylvvjs)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 855fdbd301879dfb57b48acda05967f6f6e72b8e
code hash: 00d4a46e7753dc6d4d2aadcfe98dd0bb9b5df31a6b14678346e3166191d078c6
verified: 8/19/2026, 9:08:34 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