D
Caution
42/100
11 days ago

agent-swarm

Your Company Agentic Operating System

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

desplega-ai

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
⚠️
Known vulnerabilities in dependencies: 4 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.
🔐
You'll be asked for 11 credentials: AGENTMAIL_WEBHOOK_SECRET, AGENT_SWARM_API_KEY, API_KEY, CLAUDE_CODE_OAUTH_TOKEN, EVALS_API_KEY, GITHUB_APP_PRIVATE_KEY, GITHUB_WEBHOOK_SECRET, JIRA_CLIENT_SECRET, LINEAR_CLIENT_SECRET, SLACK_APP_TOKEN, SLACK_BOT_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies4 high1 medium25 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.1GHSA-345p-7cg4-v4c7

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

high@modelcontextprotocol/sdk@1.25.1GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

highhono@4.12.3GHSA-88fw-hqm2-52qc

hono: CORS Middleware reflects any Origin with credentials when `origin` defaults to the wildcard

highhono@4.12.3GHSA-q5qw-h33p-qvwr

Hono vulnerable to arbitrary file access via serveStatic vulnerability

mediumhono@4.12.3GHSA-xf4j-xp2r-rqqx

Hono: Path traversal in toSSG() allows writing files outside the output directory

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.
configAGENTMAIL_DISABLE
🔐 secretAGENTMAIL_WEBHOOK_SECRET
configAGENT_ID
🔐 secretAGENT_SWARM_API_KEY
configALLOW_PRIVATE_NETWORK_URLS
🔐 secretAPI_KEYedit .env — set plus the credential for your chosen harness (for example CLAUDE_CODE_OAUTH_TOKEN)
configAPP_URL
configCAPABILITIES
🔐 secretCLAUDE_CODE_OAUTH_TOKENedit .env — set API_KEY plus the credential for your chosen harness (for example )
configDATABASE_PATH
configDUMMY_OAUTH_BASE_URL
🔐 secretEVALS_API_KEY
configEVALS_MAX_CONCURRENT_RUNS
configEVALS_PORT
configGITHUB_APP_ID
🔐 secretGITHUB_APP_PRIVATE_KEY
configGITHUB_DISABLE
🔐 secretGITHUB_WEBHOOK_SECRET
configHEARTBEAT_INTERVAL_MS
configJIRA_CLIENT_ID
🔐 secretJIRA_CLIENT_SECRET
configJIRA_DISABLE
configJIRA_ENABLED
configJIRA_REDIRECT_URI
configLINEAR_CLIENT_ID
🔐 secretLINEAR_CLIENT_SECRET
configLINEAR_DISABLE
configLINEAR_ENABLED
configLINEAR_REDIRECT_URI
configMCP_BASE_URL
configOAUTH_KEEPALIVE_DISABLE
configOAUTH_REFRESH_SWEEP_DISABLE
configSCHEDULER_INTERVAL_MS
configSCRIPTS_ONLY_MCP
🔐 secretSLACK_APP_TOKEN
🔐 secretSLACK_BOT_TOKEN
configSLACK_DISABLE
configSWARM_URL
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

2/2 tools missing one or more hints — ping (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); whoami (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

1/2 tool handlers declare input schemas (50%)

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

Tool handlers catch errors

Only 0/2 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

1/2 tools referenced in tests (50%)

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

Shell command execution

14 child_process calls — runs shell commands

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

Secrets not logged

8 secret values sent to console.log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 4 high severity in production deps — @modelcontextprotocol/sdk@1.25.1 (high), @modelcontextprotocol/sdk@1.25.1 (high)

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

Dependency freshness

1/42 production deps stale: @inkjs/ui@2024-05-22 (2.2y)

Domain consistency

npm scope @agent-swarm doesn't match GitHub owner desplega-ai

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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 9 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/desplega-ai-agent-swarm-1v5y64?variant=verified)](https://m8ven.ai/mcp/desplega-ai-agent-swarm-1v5y64)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 1b1860fe308788486691389918e4bdbc03744c1d
code hash: 1e6f450ae6cc6aba6ef3d8abd5b88a8256865760f05021f636e208dc9be123d1
verified: 8/8/2026, 7:23:19 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