Wargaming MCP server

awesome-servers

One repo for three families of servers, each subtree keeping its own layout and tooling so it can still be built, run and published on its own.

Most servers read public data with no key of their own; the ones wrapping a vendor API take that vendor's key. Nothing in this repo asks a caller to pay. On 2026-10-17 the licence machinery was removed for good: the per-tool src/license.ts gates are gone from the MCP servers, and the A2A and ACP trees no longer carry the hosted licence-gateway half — the skills that used it now answer with an explicit not-implemented stub. Nothing here asks a caller to pay, and nothing they run is refused with a buy link.

Nothing here is generated: each subtree's README says what its servers read, and every server has its own unit tests (mcp/servers//tests, acp/agents//tests, a2a/servers//tests) plus a live smoke check (tools/smoke.py, a2a/tools/smokeall.py).

Novel and original

Nearly all of this is first-of-its-kind work, not a port of an existing catalogue. Before each server or agent was built, it was checked against the official tool lists (the MCP registries, agentclientprotocol.com's agent list and registry) and a live GitHub search for the same domain, and the research logs record what was found and why it still counted as missing — see mcp/MISSING.md, acp/MISSING.md and a2a/docs/. Highlights:

published/; mcp/MISSING.md documents the check that preceded every build: what was searched, what was skipped and why the domain still counted as uncovered.

• The MCP side holds TypeScript servers, one npm package each, and 1039 published packages under

official list was a coding agent. These 79 Python agents are the first non-coding ACP agents, and several use protocol surfaces no other agent uses in production (session/requestpermission for dataset reads, fs/writetextfile for a briefing file, session/cancel for a conditional watch, image content blocks, a live SSE push feed), each proved-unused in the wild by search at build time. Two more firsts carry their own proof: the orchestrator is an agent whose feeds are agents* — it spawns sibling repo agents as real ACP child processes and merges their answers — and the nyc pack is the first multi-agency city surface.

• On the ACP side there were zero domain agents before this repo — every agent on the

feed probed live, with its date, what it answered and whether it still works. The published site renders that table at .

• acp/MISSING.md doubles as the public-feed atlas: every keyless

dataset, answer honestly about what the feed did and did not say, and keep the whole thing small, tested and self-contained.

• The pattern across all three subtrees is the same thesis: wrap one real, keyless public

Publishing

• MCP servers publish from mcp/servers/ (its own package.json, version and README).
• ACP and A2A servers are repo-run today (Python, no packaging step).

Built on top of it

Shortened. The full README is on GitHub.