io.github.magnusmage/cohort-mcp
NPM · COHORT-MCP
Shared AI memory for teams: a git vault of markdown, human-approved, injection-safe, local-only.
Available components
Last scanned (2 hours ago)
Scores higher than 45% of npm servers
Category Memory and Knowledge
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 13 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 269 tokens (~44/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 29 Oct 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/cohort-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cohort_load Load team context ~52
Return bounded team context from the vault, fenced as data not instructions.
| Name | Type | Req | Description |
|---|---|---|---|
| scope | string | – | Optional scope hint, reserved for future use. |
| topics | array | – | Optional topic filters to narrow the loaded context. |
No output schema declared.
No examples provided.
cohort_policy_get Read effective policy ~27
Return the caller's effective, read-only policy limits. The model cannot write policy.yml.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cohort_propose Propose a writeback ~34
Run proposed records through the server-enforced write gate.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Records to run through the write gate. |
No output schema declared.
No examples provided.
cohort_search Search the vault ~72
Search the vault, honoring readable scope. Verified-only by default; set include_quarantined to include agent-asserted records.
| Name | Type | Req | Description |
|---|---|---|---|
| include_quarantined | boolean | – | Include agent-asserted, unverified records. Default: verified only. |
| query | string | yes | Text to search for across the vault. |
No output schema declared.
No examples provided.
cohort_status Vault and policy status ~20
Report the effective policy summary and record counts from the vault.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cohort_why Explain a record's provenance ~64
Return who, which model, when, and why a record exists, read from git history. Read-only forensics.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The content-addressed record id to explain, for example f-a1b2c3d4e5f6. |
No output schema declared.
No examples provided.
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.
npm · cohort-mcp
claude mcp add magnusmage-cohort-mcp -- npx -y cohort-mcp
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.