ybkk-AIOS (01men/ybkk-AIOS) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 13 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

ybkk-AIOS

榕器 · 企业 AI 资源统一管理平台 —— dsh/cordis 插件化（IAM/OIDC/MCP/Skill 市场/Agent/审计/用量计量/模型网关/流程编排），私有化年费 + 治理包，对外只呈现用量透明与内部成本穿透

→ 01men/ybkk-AIOS· listed on github_repo_search

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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

01men

Source: github_repo_search

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

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
2 flows detected: DSHCTL_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 5 credentials: AUTHZ_CLIENT_SECRET, AUTHZ_PLATFORM_TOKEN, DSHCTL_PASS, DSHCTL_TOKEN, HERMES_AUTHZ_CLIENT_SECRET
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.
configAUTHZ_CHECK_TIMEOUT_MS
configAUTHZ_CLIENT_ID
🔐 secretAUTHZ_CLIENT_SECRET
configAUTHZ_DEGRADE
configAUTHZ_ENFORCE灰度：rules 单例 observeOnly（缺省 true，G0 双通道同步观察）/degradeAllToReadonly（G3）+ 网关 全局 kill-switch + 逐令牌 enforce；任一阶段秒级回退。
🔐 secretAUTHZ_PLATFORM_TOKEN
configAUTHZ_PLATFORM_URL
configAUTHZ_SNAPSHOT_DIR
🔐 secretDSHCTL_PASS
🔐 secretDSHCTL_TOKEN
configDSHCTL_URL
configDSHCTL_USER
configHERMES_AUTHZ_PLATFORM_URL
configHERMES_AUTHZ_CLIENT_ID
🔐 secretHERMES_AUTHZ_CLIENT_SECRET
configHERMES_AUTHZ_DEGRADE
configHERMES_AUTHZ_OBSERVE_ONLY
// 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

13/13 tools missing one or more hints — get_top_stories (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); fetch_item (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); submit_post (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +10 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 test coverage

Only 1/13 tools referenced in tests (8%)

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

Secrets stay with their owner

1 secret sent to a request target we could not resolve (DSHCTL_TOKEN → dynamic) — often a configured endpoint, not necessarily third-party

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

Secrets not logged

1 secret value sent to 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 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 Score](https://m8ven.ai/badge/mcp/01men/ybkk-aios)](https://m8ven.ai/mcp/01men/ybkk-aios)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 9e51e09fb3bb345bf56bfcccb977609b9ab94792
code hash: 5990e3f64324e5d1d9b50d94c92ec3b0a3a4a5afe027d1c78453454e7157151a
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