operating-swarm (matthewhand/operating-swarm) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 9 tools. No publisher has claimed this listing.

C
Warning
74/100

operating-swarm

Operating Swarm (OS): provider-agnostic agent operating layer and harness. Native execution, external harnesses, and peer OS instances as one abstraction.

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

matthewhand

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 →

Install from

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
🚨
Code appears obfuscated
2 files are unreadable to a human reviewer. Cannot audit what they do.
🔐
You'll be asked for 7 credentials: DJANGO_SECRET_KEY, API_AUTH_TOKEN, SWARM_API_KEY, OPENAI_API_KEY, LITELLM_API_KEY, LITE_LLM_API_KEY, REMOTE_TEAM_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes10 tools · 1 behind config

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

dynamic_tool_80
dynamic_tool_698
dynamic_tool_87
dynamic_tool_127
dynamic_tool_513
dynamic_tool_574
read_file

Read a file under the workspace (allowed for all personas).

write_file

Write a file under the workspace (encouraged for implementer personas).

list_files

List files in a workspace directory.

consult_moa_panelbehind config

Call Mixture of Agents for a read-only multi-seat consensus opinion.

// 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.
configPYTEST_CURRENT_TEST
configSWARM_COMMAND_TIMEOUT
configCAPTURE_PORT
🔐 secretDJANGO_SECRET_KEY
configCAPTURE_MANIFEST
configSWARM_TEST_MODE
configSCRATCH
configSWARM_PROBE_BASE
🔐 secretAPI_AUTH_TOKEN
🔐 secretSWARM_API_KEY
configSWARM_FLEET_SEATS_PATH
configSWARM_AGENT_SETTINGS_PATH
configSWARM_CLI
configSWARM_STDERR_LOG
configDJANGO_SETTINGS_MODULE
configSWARM_UVICORN_WORKERS
configRUN_MAIN
configSWARM_CONFIG_PATH
configLITELLM_MODEL
configOPENAI_MODEL
configDEFAULT_LLM
configSWARM_ALLOW_ANONYMOUS
configSWARM_ALLOW_USER_BLUEPRINT_DISCOVERY
configSWARM_BLUEPRINT_PATHS
configENABLE_WEBUI
configSWARM_THROTTLE_ANON
configSWARM_THROTTLE_USER
configSWARM_MAX_INFLIGHT
configDJANGO_X_FRAME_OPTIONS
configSWARM_SECURE_COOKIES
configSWARM_CSP
configENABLE_MCP_SERVER
configSWARM_DEBUG
configSWARM_ENABLE_AGENT_TRACING
configLITELLM_BASE_URL
configOPENAI_BASE_URL
configSWARM_CONFIG_DEBUG
🔐 secretOPENAI_API_KEY
configSWARM_LLM_API_MODE
configSWARM_USER_BLUEPRINT_SANDBOX
configSWARM_AGY_CONVERSATIONS_DIR
configSWARM_ENFORCE_SINGLE_WORKER
configXDG_CONFIG_HOME
🔐 secretLITELLM_API_KEY
configSWARM_GITHUB_REPO
configSWARM_DEFINITION_TEST_FIXTURE
configIMAGE_GEN_BASE_URL
configIMAGE_GEN_MODEL
configIMAGE_GEN_API_KEY_ENV
configSWARM_AGENT_RUN_TIMEOUT
configLITE_LLM_BASE_URL
🔐 secretLITE_LLM_API_KEY
configSWARM_LLM_ASSIST
configSWARM_USER_DATA_DIR
🔐 secretREMOTE_TEAM_API_KEY
configSWARM_EXPAND_REMOTES
configSWARM_PORT
configSWARM_LISTEN_URL
configHOST
configSWARM_RESPONSES_DIR
configXDG_DATA_HOME
configSWARM_ROUTER_DESIGNS
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
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

10/10 tools missing one or more hints — dynamic_tool_80 (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); dynamic_tool_698 (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); dynamic_tool_87 (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +7 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

4/10 tools referenced in tests (40%)

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

No eval / new Function

4 eval() or new Function() calls — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

Readable source code

2 files are minified or bundled, which is usually build output rather than concealment

Ship unminified, readable source.

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/matthewhand/operating-swarm?variant=verified)](https://m8ven.ai/mcp/matthewhand/operating-swarm)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 3f1259470ea059e9c6e6e18051afc20e2c21f3ee
code hash: 7c9c62687fda8ce15546a2c4692d00f23b8a6f54cf6f18b7032253e99495ca5d
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