claude-vibe-squad (mtarcure/claude-vibe-squad) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 33 tools. No publisher has claimed this listing.

C
Caution
74/100

claude-vibe-squad

Multi-model AI orchestration where behaviour is Markdown, not code. One coordinator routes scoped task packets to 71 role-based specialists across 5 model families (Codex / Claude / Gemini / Grok / Kimi) — each working in an isolated git worktree, each reviewed by a rival family before it lands. One tmux session, no server.

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

mtarcure

Source: github_topic

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
🚨
Secret credentials may flow to a network call
4 flows detected: XAI_API_KEY, PERPLEXITY_API_KEY, GH_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 8 credentials: OPENAI_API_KEY, FIRECRAWL_API_KEY, XAI_API_KEY, PERPLEXITY_API_KEY, OBSIDIAN_REST_API_KEY, GH_TOKEN, VIBESQUAD_DAEMON_TOKEN, GEMINI_API_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.
🔐 secretOPENAI_API_KEY
🔐 secretFIRECRAWL_API_KEY
configFIRECRAWL_ZERO_DATA_RETENTION
🔐 secretXAI_API_KEY
🔐 secretPERPLEXITY_API_KEY
🔐 secretOBSIDIAN_REST_API_KEY
configCHRONO_VAULT_ROOT
configVIBE_SQUAD_ROOT
configVIBE_PLUGINS
configVIBE_PYTHON
configCOVERAGE_LEDGER_STATE
configXDG_STATE_HOME
🔐 secretGH_TOKEN
configVAULT_ROOT
configVS_DASH_WIDTH
configCOLUMNS
configNO_COLOR
configVS_DASH_COLOR
configVS_DASH_SNAPSHOT_TIMEOUT
configVS_DASH_HEIGHT
configVS_DASH_HISTSTATE
configVS_DASH_HITMAP
configVS_SWARM_STATUS
configVS_DASH_CAPACITY
configVS_DASH_INPLACE
configVS_BOARD_HISTORY
🔐 secretVIBESQUAD_DAEMON_TOKEN
🔐 secretGEMINI_API_KEY
configVIBESQUAD_STATE_DIR
configCHRONO_VAULT_CLEARANCE
configCHRONO_AUTOCAPTURE_DISTILL
configCHRONO_AUTOCAPTURE_DISTILL_RESTRICTED
configVS_CANCEL_GRACE_SECONDS
configCHROME_CDP_HOST
configCHROME_CDP_PORT
configCHROME_CDP_URL
configTRUSTED_HOST_PATH
configSQUAD_BASE_BRANCH
configSTATE_DIR
configSQUAD_SESSION
configTMUX_BIN
configCHRONO_TMUX_TARGET
configRESPONSE_MIN_AGE_SECONDS
configNO_ENVELOPE_GRACE_MINUTES
configNO_ENVELOPE_MIN_DISPATCH_AGE_SECONDS
configNEVER_LAUNCHED_GRACE_SECONDS
configLOCKDIR_TIMEOUT_SECONDS
configCHRONO_CANONICAL_VAULT_ROOT
configSQUAD_RECONCILE_SWEEP_TIMEOUT_SECONDS
configSQUAD_RECONCILE_SWEEP_SECONDS
configEXPECTED_RUNTIME_ROWS
configSTRICT_ADAPTERS
// 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

33/33 tools missing one or more hints — generate_image (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); generate_video (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); openai_auth_diagnostic (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +30 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

20/33 tools referenced in tests (61%)

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

Secrets stay with their owner

1 secret/sensitive value flow into network calls (XAI_API_KEY → https://api.x.ai/v1/responses) (1 other flows matched canonical API hosts)

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

Domain consistency

npm scope @vibe-squad doesn't match GitHub owner mtarcure

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 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/mtarcure/claude-vibe-squad?variant=verified)](https://m8ven.ai/mcp/mtarcure/claude-vibe-squad)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: d5262e2151716946c582fec7dd7aedfee70b1606
code hash: 5ae9cc88ef924d12dbdfe379a0573b8ea54ddae0e66877c6dcfe9dc546409b3d
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