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

Back to MCP Trust IndexM8ven
C
Caution
74/100

swarm-mcp

MCP server that lets multiple coding-agent sessions on the same machine discover each other and collaborate through a shared SQLite database.

→ Volpestyle/swarm-mcp· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. 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

Volpestyle

Source: Glama

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

Glamanot scored here

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
⚠️
Known vulnerabilities in dependencies: 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// tools this server exposes3 tools

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.

register

Register this agent session with the swarm. Call this first before using other tools.

remove_instance

Forcefully remove another instance from the swarm. Releases its tasks and locks.

deregister

Remove this instance from the swarm and clean up its tasks and locks.

// known CVEs in dependencies2 high1 medium1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.25.2GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

highesbuild@0.24.2GHSA-gv7w-rqvm-qjhr

esbuild: Missing binary integrity verification in Deno module enables remote code execution via NPM_CONFIG_REGISTRY

mediumajv@8.17.1GHSA-2g4f-4pwh-qvx6

ajv has ReDoS when using `$data` option

lowesbuild@0.24.2GHSA-67mh-4wv8-2f99

esbuild enables any website to send any requests to the development server and read the response

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configAGENT_IDENTITY
configHERDR_FAKE_COMMAND
configHERDR_FAKE_LOG
configHERDR_FAKE_RUN_PANE
configHERDR_PANE
configHERDR_PANE_ID
configHERMES_HOST_HOME
configHERMES_PROFILE_HOME
configMERMAID_BACKGROUND
configMERMAID_SCALE
configMERMAID_WIDTH
configSWARM_CC_AGENT_ROLE
configSWARM_CC_IDENTITY
configSWARM_CODEX_AGENT_ROLE
configSWARM_CODEX_IDENTITY
configSWARM_DB_PATH
configSWARM_DISPATCH_HARNESS
configSWARM_DISPATCH_SPAWNER
configSWARM_HARNESS_CLAUDE
configSWARM_HARNESS_CODEX
configSWARM_HARNESS_HERMES
configSWARM_HARNESS_OPENCODE
configSWARM_HERDR_BIN
configSWARM_HERDR_MAX_PANES_PER_TAB
configSWARM_HERDR_PARENT_PANE
configSWARM_HERDR_SPLIT_DIRECTION
configSWARM_HERMES_IDENTITY
configSWARM_HERMES_ROLE
configSWARM_IDENTITY
configSWARM_MCP_ALLOW_CROSS_IDENTITY
configSWARM_MCP_ALLOW_UNLABELED
configSWARM_MCP_BINLauncher-managed sessions may set to a real command such as
configSWARM_MCP_DEFAULT_ROOTS
configSWARM_MCP_DIRECTORY
configSWARM_MCP_FILE_ROOT
configSWARM_MCP_INSTANCE_IDWrites (require identity — pass --as <uuid prefix unique-label-substring> or set ; falls back to the sole live instance in scope):
configSWARM_MCP_LABEL
configSWARM_MCP_LAUNCH_DIR
configSWARM_MCP_PERSONAL_ROOTS
configSWARM_MCP_PROFILE_DIR
configSWARM_MCP_SCOPEconst scope = process.env.;
configSWARM_OPENCODE_AGENT_ROLE
configSWARM_PROTOCOL_STATE_RS
configSWARM_SPAWNER
configSWARM_WORKER_HARNESS
// 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

3/3 tools missing one or more hints — register (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); remove_instance (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); deregister (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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 inputs are validated

Only 1/3 tool handlers declare input schemas (33%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool test coverage

2/3 tools referenced in tests (67%)

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

Shell command execution

68 child_process calls — runs shell commands

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

Production dependencies are patched

0 critical, 1 high severity in production deps — @modelcontextprotocol/sdk@1.25.2 (high), ajv@8.17.1 (medium)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Dependency freshness

1/6 production deps stale: ajv-formats@2024-03-30 (2.2y)

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