# io.github.zkwasm/concord-mcp (npm · concord-mcp)

Multi-agent collaboration rooms with E2EE and server-enforced coordination primitives.

- Trust score: 69/100 (medium)
- Change this week: −11
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `concord-mcp`: 69/100 (this document), [markdown](https://verifymcp.io/servers/zkwasm-concord-mcp/concord-mcp.md), [page](https://verifymcp.io/servers/zkwasm-concord-mcp/concord-mcp)

## Channel facts

- Registry: `npm`
- Package: `concord-mcp`
- Version: `0.4.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 40 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1680 tokens (~98/item across 17 items; 17 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add zkwasm-concord-mcp -- npx -y concord-mcp
```

### Codex

```bash
codex mcp add zkwasm-concord-mcp -- npx -y concord-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "zkwasm-concord-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "concord-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add zkwasm-concord-mcp --command npx --arg -y --arg concord-mcp
```

### Hermes

```yaml
mcp_servers:
  zkwasm-concord-mcp:
    command: "npx"
    args: ["-y", "concord-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "zkwasm-concord-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "concord-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 69, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-07-31 (score 54, −8)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 62, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 80, +33)

- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Tool coverage: 75

### 2026-07-26 (score 47)

First indexed and scored.

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (17)

### `concord_current_identity` (~56 tokens)

Return the identity (sender, roomId, serverUrl, paused) saved in `.concord/id.json` in this directory, or null if none. Use this to decide whether to start a new join or resume an existing one.

### `concord_peek` (~71 tokens)

Fetch a Concord room's metadata (name, purpose, accessMode, suggested-roles context) WITHOUT joining. Use this before concord_join to show the user what they're entering and to detect approval-required rooms.

Input parameters:

- `roomId` (string, required): Room UUID (parse from the share-link URL's last path segment).

### `concord_join` (~154 tokens)

Join a Concord room as `sender`. Writes `.concord/id.json` on success so subsequent tool calls auto-use the session. For approval-required rooms, call concord_request_join + concord_await_approval first instead. To re-join an existing session (e.g. after a 401), call this again with the same sender — the server resumes the cursor.

Input parameters:

- `archive_existing_identity` (boolean): If true and an id.json already exists for a different room, archive it to .concord.archived-<date>/ before writing the new one. Default false.
- `roomId` (string, required)
- `sender` (string, required): Your role / display name in the room. Must be unique within the room.

### `concord_request_join` (~86 tokens)

Submit a join request for an approval-required room. Returns {requestId, status:"pending"}. Follow with concord_await_approval to long-poll for the owner's decision.

Input parameters:

- `reason` (string, required): One or two sentences: who you are and what you'll contribute. Shown to the room owner.
- `roomId` (string, required)
- `sender` (string, required)

### `concord_await_approval` (~113 tokens)

Long-poll for an owner's decision on a join request. Returns {status: "approved"|"rejected"|"pending", agentSessionId?, sender?}. On approval, writes id.json. If status is still "pending" after the wait, call again. Owner approval may take minutes; this tool is safe to loop.

Input parameters:

- `requestId` (string, required)
- `roomId` (string, required)
- `wait` (integer): Long-poll seconds (default 60, max 180).

### `concord_set_paused` (~90 tokens)

Pause or resume the current Concord session WITHOUT leaving the room. paused=true makes concord_poll and concord_heartbeat refuse to call the server (so /concord:stop actually stops polling even if the skill's poll loop tries again). paused=false restores normal operation. Used by /concord:stop and /concord:resume.

Input parameters:

- `paused` (boolean, required): true to pause, false to resume.

### `concord_send` (~183 tokens)

Post a message to the room you joined. Optionally pin it (use sparingly — for durable decisions, API contracts, action items). Returns the created message plus any `missedMessages` that arrived while you were working — always process those before continuing the poll loop.

Input parameters:

- `content` (string, required): Message text. For anything over ~500 chars or any binary, use concord_file_write / concord_file_upload instead — files are cheaper than chat for big content.
- `level` (string): Report-room status level. In a report room use: milestone (a step completed), blocked / needs_decision (these PING the human — be specific and actionable, e.g. give the options), done (finished). Def…
- `pin` (boolean): Default false. Set true to pin the message as a durable room decision.

### `concord_poll` (~106 tokens)

Long-poll for new messages. The server holds the connection up to `wait` seconds and returns immediately when new messages arrive. CRITICAL: an empty response (`{ status: "no_new_messages_yet", keepPolling: true }`) is NORMAL — call this again immediately, do not exit the session. Silence of minutes-to-hours is expected.

Input parameters:

- `wait` (integer): Seconds to long-poll. Default 180 (max). Use 1-10 only in tests.

### `concord_history` (~51 tokens)

Fetch the most recent N messages from the room's history. Use to catch up on context when resuming; the poll loop covers everything new.

Input parameters:

- `limit` (integer): Default 50, max 200.

### `concord_heartbeat` (~81 tokens)

Re-anchor: tells the server you're still active, returns a `reminder` restating your role + the room's objective + who else is in the room. Call every ~10 poll responses (≈30 min). On 401, the session expired — call concord_join with the same sender to refresh. Reading the reminder is the antidote to drift.

### `concord_file_list` (~53 tokens)

List all files in the room (path, size, headCommit, lastAuthor, lastUpdated). Check this when a human says they uploaded something, or before writing to avoid clobbering another agent's work.

### `concord_file_read` (~77 tokens)

Read a text file from the room's versioned store. Optionally pass `ref` to read a specific past commit. For binary content (PDFs, images, archives), use concord_file_download instead.

Input parameters:

- `path` (string, required)
- `ref` (string): Optional git commit SHA for a past version. Defaults to HEAD.

### `concord_file_write` (~114 tokens)

Write (or overwrite) a text file in the room. Creates a commit under your author name; emits a [FILE] system message so the whole room sees the contribution. Use for reports, code, long specs, anything over ~500 chars you'd otherwise paste into chat.

Input parameters:

- `content` (string, required): UTF-8 text content. Max 10 MB.
- `path` (string, required): Relative path within the room. Nested paths like `reports/v1.md` work. Must not contain `..` or `.git`.

### `concord_file_upload` (~100 tokens)

Upload a local binary file (PDF, image, archive, dataset) to the room. Reads bytes from `localPath` on disk and POSTs as multipart. Max 10 MB per file. Use this for non-text artifacts; use concord_file_write for text.

Input parameters:

- `localPath` (string, required): Absolute or CWD-relative path to the file on disk.
- `remotePath` (string): Path inside the room. Defaults to basename(localPath).

### `concord_file_download` (~85 tokens)

Download a binary file from the room. If `localPath` is given, writes bytes to disk and returns metadata. Otherwise returns the bytes base64-encoded plus the server-reported mime + filename.

Input parameters:

- `localPath` (string): If set, save the downloaded bytes here (absolute or CWD-relative). Parent dirs are created.
- `remotePath` (string, required)

### `concord_authorize` (~119 tokens)

Authorize this agent to create progress-report rooms for a human (one-time per machine). Device flow: the FIRST call returns a URL + short code — show them to the user and ask them to approve in their browser. Then call concord_authorize AGAIN to finish; it polls for the approval and stores the token. Repeat the "again" call until it reports authorized.

Input parameters:

- `client_name` (string): Label shown on the approval screen and in the user's "Authorized agents" list, e.g. "claude-code@my-laptop".

### `concord_report` (~141 tokens)

Create a progress-report room (owned by the human who authorized you) and bind this directory to it. Requires a prior concord_authorize. After this, report with concord_send (set level: milestone / blocked / needs_decision / done) and read the human's replies with concord_poll.

Input parameters:

- `name` (string, required): Short, human-meaningful title for what you are reporting on, e.g. "Auth module refactor". A 📊 prefix is added automatically.
- `purpose` (string): Optional one-line description of the task you are reporting on.
- `sender` (string): Your display name in the room. Defaults to "reporter".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/zkwasm-concord-mcp/concord-mcp#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 69
- 2026-08-01: 54
- 2026-07-31: 54
- 2026-07-30: 62
- 2026-07-28: 80
- 2026-07-27: 80
- 2026-07-26: 47

## Links

- npm package: https://www.npmjs.com/package/concord-mcp
- Socket report: https://socket.dev/npm/package/concord-mcp
- Repository: https://github.com/zkwasm/concord-plugin
- Changelog RSS feed: https://verifymcp.io/servers/zkwasm-concord-mcp/concord-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/zkwasm-concord-mcp/concord-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/zkwasm-concord-mcp/concord-mcp