Arkhe-OS (arkhe-genesis/Arkhe-OS) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 39 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
10 days ago

Arkhe-OS

ASI

→ arkhe-genesis/Arkhe-OS· listed on github_code

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

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

arkhe-genesis

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

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: GRID_API_TOKEN_ID, ALTIUM_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 11 credentials: ALTIUM_API_KEY, ETHERSCAN_API_KEY, SIDECAR_TOKEN, ARKHE_CORE_SECRET_KEY, PICOADS_API_KEY, SUPERVISOR_TOKEN, ARKHE_DEMO_KEY, ARKHE_PROD_KEY, ARKHE_ENTERPRISE_KEY, GOOGLE_API_KEY, SERPAPI_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.
configALLOWED_ORIGINS
🔐 secretALTIUM_API_KEY
configALTIUM_API_URL
configDISABLE_HMR
configDISPLAY
🔐 secretETHERSCAN_API_KEY
🔐 secretSIDECAR_TOKEN
configGGUF_MODEL
configGGUF_QUANT
configGGUF_CTX
configGGUF_GPU_LAYERS
configGGUF_CACHE_DIR
configSIDECAR_HOST
configSIDECAR_PORT
configSQUADRON_NAME
configSQUADRON_ROLE
configALLOWED_OPCODES
configMETRICS_PORT
🔐 secretARKHE_CORE_SECRET_KEY
configPICOADS_API_BASE
🔐 secretPICOADS_API_KEY
🔐 secretSUPERVISOR_TOKEN
configWORLD_SIZE
configRANK
configMASTER_ADDR
configMASTER_PORT
configCUDA_VISIBLE_DEVICES
🔐 secretARKHE_DEMO_KEY
🔐 secretARKHE_PROD_KEY
🔐 secretARKHE_ENTERPRISE_KEY
configGRPC_CERT_PATH
configGRPC_KEY_PATH
configARKHE_REGION
configARKHE_NEURON_TYPE
configARKHE_EXPECTED_HASH
🔐 secretGOOGLE_API_KEY
configGOOGLE_CX
🔐 secretSERPAPI_KEY
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

39/39 tools missing one or more hints — velxio_compile_firmware (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); velxio_run_simulation (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); mirage_execute (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +36 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 8/39 tools referenced in tests (21%)

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

Shell command execution

1 call in production code run through a shell (src/browser.ts:162)

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

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/arkhe-genesis/arkhe-os)](https://m8ven.ai/mcp/arkhe-genesis/arkhe-os)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: f6ce403bfe985cc1e65afa214981cf22a6c70bee
code hash: 628debe537e2f4e39e760221278275a9c7d86a375c7be5a8a8f4f50711f917fd
verified: 9/3/2026, 4:37:17 PM
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