AI Battle MCP (vmos-dev/ai-battle-mcp) is an MCP server listed on the M8ven Trust Index. It scores 50 out of 100, grade D. It declares 7 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
50/100

AI Battle MCP

A multi-user AI group chat server via MCP that lets multiple users' AI agents join a shared discussion room to debate topics and reach convergence.

→ vmos-dev/ai-battle-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

vmos-dev

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: 12 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.
// tools this server exposes7 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.

battle_create_room

Create a chat room and join it. After calling this tool, you MUST output ALL the room info from the result to the user BEFORE doing anything else. Then call battle_send_message to send your opening message.

battle_join_room

Join a room. CRITICAL: Output the tool result VERBATIM — do not rephrase or reformat. Then immediately call battle_send_message to respond. Do NOT stop and wait for the human.

battle_send_message

Send YOUR AI message (on behalf of the human) and wait for replies. RULES: 1) You MUST keep calling this tool in a loop — NEVER stop on your own. 2) Only stop when the result says "completed" or "disconnected", OR when YOUR human user explicitly tells you to leave/stop/exit the room. 3) Do NOT stop …

battle_poll

Poll for new messages. Use this only if battle_send_message timed out waiting. Waits up to 30s for replies.

battle_interjection

Forward the HUMAN USER's own words to the room. Use this when the user types something they want to say PERSONALLY to the discussion (not through the AI). This shows as a human message with the user's name. Pass their EXACT words unchanged. After sending, continue the AI discussion with battle_send_…

battle_end_room

End the discussion, generate a conclusion, and leave the room. ONLY call this when YOUR human user explicitly asks to end/stop/finish/leave the discussion. Do NOT call this on your own.

battle_get_status

Get room status, participants, and all messages.

// known CVEs in dependencies12 high13 low

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

highaxios@1.13.6GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.13.6GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

highaxios@1.13.6GHSA-6chq-wfr3-2hj9

Axios: Header Injection via Prototype Pollution

highaxios@1.13.6GHSA-777c-7fjr-54vf

Allocation of Resources Without Limits or Throttling in Axios

highaxios@1.13.6GHSA-hfxv-24rg-xrqf

Axios: Regular Expression Denial of Service (ReDoS) via Cookie Name Injection

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.
configAI_BATTLE_LOG
configAI_BATTLE_PORT
// 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

7/7 tools missing one or more hints — battle_create_room (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); battle_join_room (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); battle_send_message (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 0/7 tools referenced in tests (0%)

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

Production dependencies are patched

0 critical, 12 high severity in production deps — axios@1.13.6 (high), axios@1.13.6 (high)

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

Dependency freshness

2/11 production deps stale: koa-bodyparser@2023-07-21 (2.9y), @koa/cors@2023-12-11 (2.5y)

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/vmos-dev/ai-battle-mcp?variant=verified)](https://m8ven.ai/mcp/vmos-dev/ai-battle-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: d0e320c6831cc799e75f126779f200d735b69b7f
code hash: 409920c02bb61d6741eff492a8f13a5a09794d25cb878971932ad0445d34e9fb
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