io.github.ydnikolaev/a2ahub
io.github.ydnikolaev/a2ahub
Is the io.github.ydnikolaev/a2ahub MCP server down? Yes. It has given no valid answer since 2026-10-30: not found.
Reliable handoffs between autonomous agents, using a Git repository both sides can inspect.
not found down since 2026-10-30 · probed 2026-11-14 · unchanged since 2026-11-12
command not found: server/a2a
- Bundle
- https://github.com/ydnikolaev/a2ahub/releases/download/v0.27.4/a2a-darwin-amd64.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
- Host
- github.com
- Repository
- https://github.com/ydnikolaev/a2ahub
- Registry
- active, updated 2026-11-11 · registry entry
Compare this server with others.
More servers
Other registry entries on github.com, the ones next to this name; all of them.
- DeepSeek Visionary io.github.xlight/deepseek-visionary · not found
- Dropify io.github.xozxro/dropify-mcp · alive
- XTELL Serial io.github.xtell-cn/xtell-serial · error
- xaffinity MCP io.github.yaniv-golan/xaffinity-mcp · alive
- Codex Bridge io.github.yeyuancc0-glitch/codex-bridge · crashed on start
- Banana Peel io.github.ygdotcom/banana-peel-mcp · alive
- wa — safe WhatsApp automation io.github.yolo-labz/wa · crashed on start
- VoxelSieve io.github.yoshi5534/voxelsieve · crashed on start
Servers that mention autonomous or repository.
- ai.agentrapay/agentra · needs auth
- ai.docuwriter/docuwriter · needs auth
- Fodda Deep Research ai.fodda/deep-research · needs auth
- gethal.ai ai.gethal/mcp · alive
- ai.inflowpay.app/inflow · needs auth
- ai.openhelm/deep-research · needs auth
- ai.openhelm/openhelm · needs auth
- ai.openhelm/seo-growth · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-30, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.