Agent Comms
Agent Comms is an MCP server published by ExaDev, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.
Does Agent Comms support the current MCP specification (2026-07-28)?
Not yet confirmed. Agent Comms is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is Agent Comms a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for Agent Comms (as of 2026-08-20).
How do I connect to Agent Comms?
Agent Comms is available via the package npm:agent-comms, the official MCP Registry under io.github.ExaDev/agent-comms, the source repository at https://github.com/exadev/agent-comms. Authentication: unknown. Transports: stdio.
Does Agent Comms support MCP revision 2025-11-25?
Yes. Agent Comms supports MCP revision 2025-11-25 (checked 2026-08-20).
Does Agent Comms support MCP revision 2026-07-28?
No. Agent Comms was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were Agent Comms's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
Cross-harness communication mesh for LLM agents - rooms, DMs, presence, and visibility over TCP
Which MCP spec revisions does Agent Comms support?
Agent Comms has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is Agent Comms?
Ranked #126 in The MCP 500 with Adoption Index 53.98 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| npm downloads (weekly) | 4,300 | API · |
| GitHub stars | 20 | API · |
| GitHub forks | 6 | API · |
| Last push | 2026-09-15T14:01:12Z | API · |
| Repository archived | no | API · |
Repository and package signals for Agent Comms
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Created
- Open issues
- 13
- Primary language
- TypeScript
- Continuous integration
- Present
- Tests
- None detected
- Security policy
- None
Declared topics: agents, communication, cross-harness, llm, mcp, mesh, presence, real-time, rooms, tcp — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
1.24.2- Last published
- First published
- Releases
- 58
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 5
- Unpacked size
- 1.2 MB
- Registry signature
- Signed
- Build provenance
- Attested
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.ExaDev/agent-comms at version 1.24.2 - lists package npm:agent-comms and repository https://github.com/exadev/agent-comms - accessed
- npm registry metadata for agent-comms at published version 1.24.2, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.29.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.29.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed