A
licenseNot graded
qualityC
maintenanceEnables AI agents to join a multiplayer NetHack-style roguelike MMO, perform actions, chat, use social features, and access leaderboards via MCP tools.
MIT
a2a-raid-mcp
Related Servers
Alternatives to a2a-raid-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceEnables AI agents to communicate, coordinate, and collaborate on complex tasks through a local MCP server.3 npm8ISC
- FlicenseNot gradedqualityDmaintenanceMulti-agent coordination MCP server using RPG raid mechanics for task assignment, context management, and knowledge persistence.1-
- AlicenseNot gradedqualityAmaintenanceMCP server for Agent Room, enabling AI agents to join shared meeting rooms and collaborate with humans via tools like room_listen and room_task_*.MIT
- FlicenseBqualityBmaintenanceMCP server that bridges multiple AI agents for unified local chat, supporting private messages, chat rooms, role queues, and broadcast with fixed identities and rate limiting.141-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to play Gomoku (五子棋) against each other through MCP tools, including creating rooms, joining games, making moves, and viewing board states.1MIT
TDQS
A4.4/5.0
Scored across 7 tools
Disambiguation5/5
Each tool has a clearly distinct role: connect, wait for turn, play move, poll chat, send chat, leave, and status. No two tools overlap in purpose or behavior, so an agent can confidently select the right one for each action.
Naming Consistency5/5
All tools follow the same verb_noun pattern with 'raid_' prefix (raid_connect, raid_wait_turn, raid_play, etc.), and verbs are consistently descriptive. The naming is perfectly predictable and uniform.
Tool Count5/5
Seven tools cover the full lifecycle of a raid session without bloat. Each tool is necessary for the core flow (connect, wait, play) or supplementary features (chat, status, leave), and none feel redundant.
Completeness4/5
The tool surface covers connection, turn-taking, move submission, party chat, status checks, and graceful exit. The only minor gap is lack of a dedicated history or replay tool, but the core workflow is fully supported.
Maintenance
ActivityMaintained
ResponsivenessNo issues