# io.github.magnusmage/cohort-mcp (npm · cohort-mcp)

Shared AI memory for teams: a git vault of markdown, human-approved, injection-safe, local-only.

- Trust score: 73/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `cohort-mcp`: 73/100 (this document), [markdown](https://verifymcp.io/servers/magnusmage-cohort-mcp/cohort-mcp.md), [page](https://verifymcp.io/servers/magnusmage-cohort-mcp/cohort-mcp)

## Channel facts

- Registry: `npm`
- Package: `cohort-mcp`
- Version: `0.1.0`
- 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-11-05.

- **Supply Chain Security**: 98/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.
  - 30 of 94 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 13 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 269 tokens (~44/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.magnusmage/cohort-mcp server?

io.github.magnusmage/cohort-mcp runs locally as an npm package, launched with npx -y cohort-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add magnusmage-cohort-mcp -- npx -y cohort-mcp
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "magnusmage-cohort-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "cohort-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add magnusmage-cohort-mcp -- npx -y cohort-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add magnusmage-cohort-mcp --command npx --arg -y --arg cohort-mcp
```

### Hermes

```yaml
mcp_servers:
  magnusmage-cohort-mcp:
    command: "npx"
    args: ["-y", "cohort-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "magnusmage-cohort-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "cohort-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add magnusmage-cohort-mcp -t stdio -c npx -a -y cohort-mcp
```

### Other

```json
{
  "mcpServers": {
    "magnusmage-cohort-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "cohort-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-11-05 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 69)

First indexed and scored.

## MCP tools (6)

### `cohort_load` (~52 tokens)

Load team context

Return bounded team context from the vault, fenced as data not instructions.

Input parameters:

- `scope` (string): Optional scope hint, reserved for future use.
- `topics` (array): Optional topic filters to narrow the loaded context.

### `cohort_propose` (~34 tokens)

Propose a writeback

Run proposed records through the server-enforced write gate.

Input parameters:

- `items` (array, required): Records to run through the write gate.

### `cohort_status` (~20 tokens)

Vault and policy status

Report the effective policy summary and record counts from the vault.

### `cohort_policy_get` (~27 tokens)

Read effective policy

Return the caller's effective, read-only policy limits. The model cannot write policy.yml.

### `cohort_search` (~72 tokens)

Search the vault

Search the vault, honoring readable scope. Verified-only by default; set include_quarantined to include agent-asserted records.

Input parameters:

- `include_quarantined` (boolean): Include agent-asserted, unverified records. Default: verified only.
- `query` (string, required): Text to search for across the vault.

### `cohort_why` (~64 tokens)

Explain a record's provenance

Return who, which model, when, and why a record exists, read from git history. Read-only forensics.

Input parameters:

- `id` (string, required): The content-addressed record id to explain, for example f-a1b2c3d4e5f6.

## Diagnostics

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

## Score history

- 2026-11-05: 73
- 2026-11-04: 72
- 2026-11-03: 72
- 2026-11-02: 71
- 2026-11-01: 71
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 69

## Common questions

### What is the io.github.magnusmage/cohort-mcp server?

io.github.magnusmage/cohort-mcp is listed in the public MCP registry as io.github.magnusmage/cohort-mcp. Shared AI memory for teams: a git vault of markdown, human-approved, injection-safe, local-only. This page covers its npm package (cohort-mcp).

### Is the io.github.magnusmage/cohort-mcp server safe to use?

io.github.magnusmage/cohort-mcp scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.magnusmage/cohort-mcp server expose?

io.github.magnusmage/cohort-mcp exposes 6 tools: cohort_load, cohort_propose, cohort_status, cohort_policy_get, cohort_search, cohort_why. Their descriptions and schemas cost roughly 269 tokens of context every time the server is loaded.

### Is the io.github.magnusmage/cohort-mcp server still maintained?

io.github.magnusmage/cohort-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.magnusmage/cohort-mcp server under?

io.github.magnusmage/cohort-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

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