2 findingsStatic scanned
Adds Storybook component and story documentation tools to an MCP server you run yourself.
9.4M installs/moMIT
Agent Coord MCP
davidbalzan · MCP server
Agent Coord MCP is a file-backed server for coordinating multiple AI coding agents. Each agent joins with an id, project and role, then can message another agent's inbox, post to shared channels that have topics and rules, add to a status stream and wait for new messages. An agent can read what another agent's pane shows, and under tmux it can send that agent a slash command to clear or compact its context.
Written by ooruby from the README of agent-coord-mcp 0.26.45.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Several coding agents on one project can share messages, decisions and status through a single server.
What you could do with it
- Have each agent join a shared channel and post decisions and status notes the others can read.
- Send one agent a direct message to its inbox, then wait for its reply.
- Send a clear or compact command into a sub-agent's session when it runs under tmux.
Written from its documentation: what it says it can do, not what our checks found.
What else was checked
Publisher and name
Nothing found across 5 checks run. Checked 2026-10-11.
Maintenance
MaintainedLast release 6 Oct 2026 (0.26.45), 4 days before this check on 11 Oct 2026.
Read from the npm registry's publish history, read by the nightly publisher check.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Command execution is bounded
- inventory
- node child_process (src/commit-cite.ts:20)
- synchronous shell execution (src/commit-cite.ts:31)
- node child_process (src/server-identity.ts:23)
- synchronous shell execution (src/server-identity.ts:75)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
- Tool description integrity
- nothing to read
- Pattern set 1.0 matched nothing on 2026-10-11, but none of the descriptions the package ships runs to 120 characters, so there was little for a rule to read.
- It reads the descriptions the package ships, not what the server says when it runs, and a clean description is not the same thing as a safe tool.
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Tool descriptions are read with pattern set v1.0, published with every rule, its sources and how often it has been wrong.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
File-backed MCP server for coordinating multiple AI coding agents (Claude Code, Cursor, Cline, etc.). Local stdio or networked over Streamable HTTP.
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.26.45, the file with digest sha512-Q22mOiL4DBDAPUebkSQ3WKO62/28duWDT/z3cxbCKwBtTfe+3HDRGLFz5D84hb969uEWLDWLXVbZNx+zslBwfg==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Paste this into your client's MCP configuration.
{
"mcpServers": {
"coord-chat": {
"command": "npx",
"args": [
"-y",
"-p",
"agent-coord-mcp@0.26.45",
"coord-chat"
]
}
}
}Or run it directly.
npx -y -p agent-coord-mcp@0.26.45 coord-chatPinned to 0.26.45, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
5,518 installs last month · no published advisories · version current · checked 2026-10-11
Where this came from
- Registry
- npm
- Package
- agent-coord-mcp
- Version read
- 0.26.45
- Resolved
- 2026-10-10
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/agent-coord-mcp)About this listing
- Kind
- MCP server
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-06
Similar MCP servers
All MCP serversVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.