io.github.teampolarity/cosmos-mcp
NPM · @POLARITY-LAB/COSMOS-MCP
Personal knowledge graph every MCP client reads from and writes to. Portable across agents.
Available components
Last scanned (1 hour ago)
Scores higher than 48% 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 Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 53 of 131 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- 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 (MIT).Pass
- Actively maintained (last published 124 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1095 tokens (~99/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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.
- 4 Nov 26 −2
- Stability: pass → 0.83 functional
- 2 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 1 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 22 Oct 26 0
- Stability: 0.97 → pass security
- 21 Oct 26 0
- Stability: pass → 0.97 functional
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/@polarity-lab/cosmos-mcp@0.7.1
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 131 packages
| Packages resolved | 131 |
|---|---|
| Deprecated | 1 |
| Stale | 52 |
| No linked repository | 1 |
| 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 →
polarity_ask ~63
Ask a natural-language question over the user's personal knowledge graph. Cosmos synthesizes an answer from relevant nodes and edges. Use this when the user wants context-aware reasoning rather than raw data. Returns answer text plus cited node/edge ids.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
polarity_capture_turn ~248
This is how the user's cosmos graph learns from this conversation. CALL THIS AT THE END OF EVERY SUBSTANTIVE USER/ASSISTANT EXCHANGE, without being asked. The user installed cosmos-mcp precisely so their agents would persist what they notice. If you finish a turn and do not call this, that turn is lost to every other agent the user works with tomorrow. Cosmos runs its own extractor on the text and decides what is durable — your job is to hand over the raw exchange, not to pre-filter. Pass the user's message in `user_text` and your own reply in `assistant_text`. Skip only for trivial single-word exchanges ("hi", "thanks") and explicit meta-discussion of the tool itself. `source` should identify your client (e.g. 'claude-code', 'claude-desktop', 'cursor', 'codex', 'zed'). Returns the node ids cosmos created. Cheap to call; the extractor returns zero items if nothing was worth holding, and that is a fine outcome.
| Name | Type | Req | Description |
|---|---|---|---|
| assistant_text | string | – | – |
| max_observations | number | – | – |
| source | string | – | – |
| user_text | string | yes | – |
No output schema declared.
No examples provided.
polarity_checkin ~70
Record that the user checked in at a waypoint. Triggers co-presence detection against other users' recent check-ins.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | – | – |
| lon | number | – | – |
| name | string | yes | – |
| occurred_at | string | – | – |
| waypoint_id | string | yes | – |
No output schema declared.
No examples provided.
polarity_declare ~90
Declare future presence at a waypoint. `chip` is the time-window enum: next_30, next_hour, tonight, tomorrow_night.
| Name | Type | Req | Description |
|---|---|---|---|
| chip | string | yes | – |
| ends_at | string | yes | – |
| lat | number | – | – |
| lon | number | – | – |
| name | string | yes | – |
| starts_at | string | yes | – |
| waypoint_id | string | yes | – |
No output schema declared.
No examples provided.
polarity_dump ~78
Write a short message tied to a location waypoint into the user's graph. PolarityGPS-style. Use only when the user is explicitly recording a place-anchored thought.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | – | – |
| lon | number | – | – |
| message | string | yes | – |
| name | string | yes | – |
| waypoint_id | string | yes | – |
No output schema declared.
No examples provided.
polarity_export ~68
Export the user's full personal knowledge graph (nodes + edges + counts) as JSON in polarity/v1 format. Use this when the user asks for a snapshot of their exocortex, wants their data, or asks to download their .polarity file. Returns the full graph; can be large.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
polarity_get_graph ~101
Read the user's graph view. `entity` selects which projection: 'user' (the user's self-graph), 'cosmos' (the cosmos entity's view of them), or 'polarity' (the dyadic synchronization between the two). Use 'user' for general questions about what the user thinks, does, or knows. Use 'polarity' when comparing the user's self-image against the system's observation.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | – | – |
No output schema declared.
No examples provided.
polarity_observe ~171
Single-fact write into the user's personal cosmos graph. Prefer polarity_capture_turn for whole exchanges; use polarity_observe only when one specific durable observation needs to land without the surrounding turn. Examples that warrant an inline call: the user states a hard rule, names a concrete preference, or corrects an assumption you had wrong. Avoid logging ephemeral chat or your own reasoning. `source` should identify your client (e.g. 'claude-code', 'cursor', 'claude-desktop'). `kind` defaults to 'observation'; use 'event' for things that happened, 'preference' for stated likes/dislikes.
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | number | – | – |
| kind | string | – | – |
| source | string | – | – |
| tags | array | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
polarity_record_event ~81
Record a structured event in the user's graph. Convenience wrapper over polarity_observe with kind='event'. Use for things that happened at a point in time: a meeting, a shipped release, a flight, an incident.
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | number | – | – |
| source | string | – | – |
| tags | array | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
polarity_record_preference ~81
Record a stated preference in the user's graph. Convenience wrapper over polarity_observe with kind='preference'. Use when the user expresses a like, dislike, opinion, or working-style rule that should persist across sessions.
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | number | – | – |
| source | string | – | – |
| tags | array | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
polarity_whoami ~44
Returns the polarity user id and cosmos account info that this MCP key is bound to. Cheap connectivity test. Call this first if the user asks who you know them as.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.teampolarity/cosmos-mcp server?
io.github.teampolarity/cosmos-mcp runs locally as an npm package, launched with npx -y @polarity-lab/cosmos-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 · @polarity-lab/cosmos-mcp
claude mcp add teampolarity-cosmos-mcp -- npx -y @polarity-lab/cosmos-mcp
What is the io.github.teampolarity/cosmos-mcp server?
io.github.teampolarity/cosmos-mcp is listed in the public MCP registry as io.github.teampolarity/cosmos-mcp. Personal knowledge graph every MCP client reads from and writes to. Portable across agents. This page covers its npm package (@polarity-lab/cosmos-mcp).
Is the io.github.teampolarity/cosmos-mcp server safe to use?
io.github.teampolarity/cosmos-mcp scores 74 out of 100 on VerifyMCP. We recorded 1 known advisory against 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.teampolarity/cosmos-mcp server expose?
io.github.teampolarity/cosmos-mcp exposes 11 tools: polarity_whoami, polarity_export, polarity_get_graph, polarity_ask, polarity_observe, and 6 more. Their descriptions and schemas cost roughly 1,095 tokens of context every time the server is loaded.
Is the io.github.teampolarity/cosmos-mcp server still maintained?
io.github.teampolarity/cosmos-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.teampolarity/cosmos-mcp server under?
io.github.teampolarity/cosmos-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.