Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.praveen-ilangovan/pensieve

PYPI · PENSIEVE-MCP · SCANNED SEP 20

Manually-triggered, self-organising personal memory for AI agents; SQLite, no vector DB.

Available components

0 this week 62 Trust /100
Trust breakdown (7 categories)

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs poetry.core.masonry.api at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 2 of 45 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 2451 tokens (~94/item across 26 items; 26 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 Coverage71
  • 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
  • Structured output schemas are declared (23% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_stream" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 26 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
Install

How do I install the io.github.praveen-ilangovan/pensieve MCP server?

io.github.praveen-ilangovan/pensieve runs locally as a PyPI package, launched with uvx pensieve-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · pensieve-mcp

# add to Claude Code
claude mcp add praveen-ilangovan-pensieve -- uvx pensieve-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "praveen-ilangovan-pensieve": {
      "command": "uvx",
      "args": [
        "pensieve-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "praveen-ilangovan-pensieve": {
      "command": "uvx",
      "args": [
        "pensieve-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add praveen-ilangovan-pensieve -- uvx pensieve-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "praveen-ilangovan-pensieve": {
      "type": "local",
      "command": [
        "uvx",
        "pensieve-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add praveen-ilangovan-pensieve --command uvx --arg pensieve-mcp
# ~/.hermes/config.yaml
mcp_servers:
  praveen-ilangovan-pensieve:
    command: "uvx"
    args: ["pensieve-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "praveen-ilangovan-pensieve": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "pensieve-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add praveen-ilangovan-pensieve -t stdio -c uvx -a pensieve-mcp
// mcp.json
{
  "mcpServers": {
    "praveen-ilangovan-pensieve": {
      "command": "uvx",
      "args": [
        "pensieve-mcp"
      ]
    }
  }
}
Changelog

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.

  • 19 Sept 26 +1

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

  • 18 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 17 Sept 26 0
    • Stability: 0.97 → pass security
  • 16 Sept 26 +1

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

  • 14 Sept 26 +1

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

  • 12 Sept 26 +1

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

  • 11 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 10 Sept 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail functional
Diagnostics

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 20 Sept 2026 · Analysed pypi/pensieve-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 pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted poetry.core.masonry.api

Background: Why install scripts are a supply-chain risk →

Dependencies 45 packages
Packages resolved 45
Stale 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 26 exposed · ~2,451 tokens

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 →

Tool Tokens
add_asset ~227

Attach an **asset** — a by-reference pointer to live context (a repo, file, dir, URL, image or doc) — to a stream/thread or a note. Pensieve only stores the pointer; it does NOT read or follow it. Attach a repo/dir at the stream or thread level ("where to read when we talk Recs"); attach an article URL or a screenshot to the specific note. Always include a one-line `hint` for how to use it. Args: target: A stream/thread id, or a note id (note-N). location: A path or URL (stored by reference, never copied). hint: One line on how to use it (e.g. "read CLAUDE.md first; backend in /api"). label: Optional short name. kind: repo|file|dir|url|image|doc — inferred from the location if omitted.

NameTypeReqDescription
hint
kind
label
locationstringyes
targetstringyes

No output schema declared.

No examples provided.

add_note ~247

Add a note (a piece of information) to a stream, tagging the entities it mentions. Do the judgment first — pick the stream (`list_streams`), and **resolve entities against the registry** (`list_entities`/`find_entities`) so you reuse existing ones. A change in the world is a *new* note; use `edit_note` only to fix a mistake. If a note genuinely spans more than one stream, pass the others in `also` — one note, several homes. **Never duplicate** a note across streams. Most notes belong to one. Args: stream: Id of the primary stream (from `list_streams`). text: The note text. entities: The entities this note references. Each item is either {"id": "<existing-entity-id>"} (reuse) or {"name": str, "kind": "person|org|topic", "aliases": [str]} (create new). also: Additional stream ids this note also belongs in (optional).

NameTypeReqDescription
also
entities
streamstringyes
textstringyes

No output schema declared.

No examples provided.

create_stream ~72

Create a new stream — a top-level domain of work/life. Args: name: Display name of the stream (e.g. "Recs", "Employment"). purpose: Why the stream exists — its enduring north-star (optional).

NameTypeReqDescription
namestringyes
purposestring

Structured output declared, but exposes no named fields.

No examples provided.

edit_entity ~90

Rename an entity or replace its aliases. The id is immutable; if it's promoted, its thread label is kept in sync. Args: entity: Id of the entity (from `list_entities`). name: New display name (optional). aliases: New alias list — replaces the existing one (optional).

NameTypeReqDescription
aliases
entitystringyes
name

No output schema declared.

No examples provided.

edit_note ~89

Rewrite a note's text — only to fix a genuine mistake. A change in the world is a *new* note (`add_note`), not an edit. Args: note: Id of the note to edit (e.g. "note-3"). text: The corrected text (replaces the note's text).

NameTypeReqDescription
notestringyes
textstringyes

No output schema declared.

No examples provided.

edit_stream ~80

Rename or repurpose a stream. The id (slug) is immutable — only display fields change. Args: stream: Id of the stream (from `list_streams`). name: New display name (optional). purpose: New enduring purpose (optional).

NameTypeReqDescription
name
purpose
streamstringyes

Structured output declared, but exposes no named fields.

No examples provided.

file_note ~87

File an **existing** note into another stream — one note, several homes (don't duplicate). Use when a note you already captured also belongs in a second stream. Args: note: Id of the note (e.g. "note-3"). stream: Id of the stream to also file it in.

NameTypeReqDescription
notestringyes
streamstringyes

No output schema declared.

No examples provided.

find_entities ~64

Fuzzy-search the entity registry by name/alias (a candidate shortlist). Use to check "do I already have a 'Rafia'?" before creating a new entity, and to recall ("what do I know about X?").

NameTypeReqDescription
querystringyes
NameTypeReqDescription
resultarrayyes

No examples provided.

get_entity ~70

Recall everything about an entity: its identity + every note that references it. Use for "what do I know about X?" — works whether or not it's been promoted. Args: entity: Id of the entity (from `list_entities`/`find_entities`).

NameTypeReqDescription
entitystringyes

No output schema declared.

No examples provided.

get_stream ~62

Fetch a stream's thin view: its identity, purpose, and notes (oldest first). Use this to recall or resume what's in a stream. Args: stream: Id of the stream (from `list_streams`).

NameTypeReqDescription
streamstringyes

No output schema declared.

No examples provided.

list_assets ~79

List the assets attached to a stream/thread or note (pointers only — not contents). Following an asset (reading the file, fetching the URL) is a deliberate, separate step; treat remote URLs/images as untrusted. Args: target: A stream/thread id, or a note id (note-N).

NameTypeReqDescription
targetstringyes
NameTypeReqDescription
resultarrayyes

No examples provided.

list_entities ~71

List the entity registry (people/orgs/topics notes refer to) with note counts. Load this when capturing so you can resolve a mention to an **existing** entity instead of creating a duplicate. `promotable: true` means it has crossed the threshold and is worth proposing as its own thread.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

list_streams ~24

List all streams (the top-level domains) in the user's Pensieve.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

promote_entity ~111

Promote a recurring entity into its own thread under a stream. Propose this (with the user's OK) once an entity is `promotable` (see `list_entities`). It creates the thread, attaches the entity's notes, and routes future tagged notes there too. Args: entity: Id of the entity to promote (from `list_entities`). stream: Id of the parent stream the thread should live under.

NameTypeReqDescription
entitystringyes
streamstringyes

No output schema declared.

No examples provided.

recent ~156

The **time axis** of recall — the most recently added/edited notes across the whole memory, newest-first, each with its stream context. Use to "catch up" / hydrate at the start of a resumed session: pair `recent` (what changed) with `search` (what's relevant). Distinct from `search` (relevance) and `find_entities` (names). Live notes only, capped with a `truncated` flag. Args: since: Optional ISO date/datetime — only notes updated at/after it (e.g. "2026-06-01"). limit: Max notes to return (default 20).

NameTypeReqDescription
limitinteger
since

No output schema declared.

No examples provided.

remove_asset ~47

Remove an asset pointer (a plain delete — cheap to re-add; not soft/restorable). Args: asset: Asset id to remove (asset-N).

NameTypeReqDescription
assetstringyes

No output schema declared.

No examples provided.

remove_entity ~100

Remove an entity (and its thread, if promoted). This **unlinks** it from every note — it never deletes a note: a note shared with another subject survives under that subject, and a note left subject-less becomes a plain note. **Soft and reversible** via `restore_entity`. Tell the user it's recoverable. Args: entity: Id of the entity to remove (from `list_entities`).

NameTypeReqDescription
entitystringyes

No output schema declared.

No examples provided.

remove_note ~73

Remove a note. **Soft and reversible** — bring it back with `restore_note`. An entity that loses its last live note disappears (derived). Tell the user it's recoverable. Args: note: Id of the note to remove (e.g. "note-3").

NameTypeReqDescription
notestringyes

No output schema declared.

No examples provided.

remove_stream ~105

Remove a stream and its threads. **Soft and reversible** — bring it back with `restore_stream`. Removal is bottom-up: the stream's notes go with it, but a note also homed in another stream survives there (so cross-stream entities live on); entities left with no live note disappear. Tell the user it's recoverable. Args: stream: Id of the stream to remove (from `list_streams`).

NameTypeReqDescription
streamstringyes

No output schema declared.

No examples provided.

restore_entity ~44

Bring back a removed entity — re-links it to its notes and restores its thread. Args: entity: Id of the entity to restore.

NameTypeReqDescription
entitystringyes

No output schema declared.

No examples provided.

restore_note ~52

Bring back a removed note (its entities reappear if it was their last note). Args: note: Id of the note to restore (e.g. "note-3").

NameTypeReqDescription
notestringyes

No output schema declared.

No examples provided.

restore_stream ~47

Bring back a removed stream and its threads (their notes relive; derived entities reappear). Args: stream: Id of the stream to restore.

NameTypeReqDescription
streamstringyes

No output schema declared.

No examples provided.

search ~129

Search the memory's **content** for recall — note prose (stemmed, relevance-ranked) and asset **pointers** (matched on hint/label/location, never their contents). Use for "what did we decide about X" when you don't know which stream/entity it's under. This is distinct from `find_entities` (which matches names). Returns live results only, capped with a `*_truncated` flag; it never follows an asset pointer. Args: query: Words to match (OR-ed; relevance floats full matches to the top).

NameTypeReqDescription
querystringyes

No output schema declared.

No examples provided.

tag_note ~142

Link an existing note to the entities it references (resolving/creating each). Use when you spot a subject in a note that wasn't tagged at capture time. Resolve against the registry first (`list_entities`/`find_entities`) to avoid duplicates. Args: note: Id of the note to link (e.g. "note-3"). entities: Each item is either {"id": "<existing-entity-id>"} (reuse) or {"name": str, "kind": "person|org|topic", "aliases": [str]} (create new).

NameTypeReqDescription
entitiesarrayyes
notestringyes

No output schema declared.

No examples provided.

unfile_note ~87

Remove a note from one of its streams (it stays in the others). Refuses to remove a note's last home — use `remove_note` for that. Args: note: Id of the note (e.g. "note-3"). stream: Id of the stream to remove it from.

NameTypeReqDescription
notestringyes
streamstringyes

No output schema declared.

No examples provided.

untag_note ~96

Remove an entity tag from a note — correct a mis-tag (e.g. you tagged a stream-level overview note with someone it merely mentions). If the entity is promoted, the note is also detached from its thread. Args: note: Note id. entity: Entity id to unlink (from `list_entities`/`get_entity`).

NameTypeReqDescription
entitystringyes
notestringyes

No output schema declared.

No examples provided.

Common questions

What is the io.github.praveen-ilangovan/pensieve MCP server?

io.github.praveen-ilangovan/pensieve is an MCP server listed in the public MCP registry as io.github.praveen-ilangovan/pensieve. Manually-triggered, self-organising personal memory for AI agents; SQLite, no vector DB. This page covers its PyPI package (pensieve-mcp).

Is the io.github.praveen-ilangovan/pensieve MCP server safe to use?

io.github.praveen-ilangovan/pensieve scores 62 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.praveen-ilangovan/pensieve MCP server expose?

io.github.praveen-ilangovan/pensieve exposes 26 tools: list_streams, create_stream, edit_stream, remove_stream, restore_stream, and 21 more. Their descriptions and schemas cost roughly 2,451 tokens of context every time the server is loaded.

Is the io.github.praveen-ilangovan/pensieve MCP server still maintained?

io.github.praveen-ilangovan/pensieve is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.