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.Icaro0310/devin-memory

PYPI · DEVIN-MEMORY-MCP

Anti-poisoning memory for agents: provenance, conflicts, quarantine gate.

Available components

+2 this week 75 Trust /100

Last scanned (17 hours ago)

Scores higher than 71% of PyPI servers

Category Memory and Knowledge

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 Security97
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 3 of 3 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency23
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 528 tokens (~40/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 3 Nov 26 0
    • Stability: 0.97 → pass security
  • 2 Nov 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.

  • 30 Oct 26 +1

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

  • 28 Oct 26 +1

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

  • 26 Oct 26 +1

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

  • 24 Oct 26 +1

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

  • 22 Oct 26 +1

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

  • 20 Oct 26 +1

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

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 4 Nov 2026 · Analysed pypi/devin-memory-mcp@0.3.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

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

Dependencies 3 packages
Packages resolved 3
No linked repository 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~528 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
approve ~23

Promote a proposed extraction to active memory.

NameTypeReqDescription
entry_idintegeryes–

No output schema declared.

No examples provided.

conflicts ~19

Contradiction pairs linked at retain time (both kept).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

extract ~59

Mine a Devin session (read-only sessions.db) for durable knowledge -> proposed entries awaiting approve.

NameTypeReqDescription
auto_approveboolean––
latestboolean––
session_idstring––
sessions_dbstringyes–

No output schema declared.

No examples provided.

list ~40

List memory entries, optionally by status (active, proposed, quarantined, retracted).

NameTypeReqDescription
limitinteger––
statusstring––
NameTypeReqDescription
resultarrayyes–

No examples provided.

prime ~43

Compact recalled-context block for a workspace — global plus workspace-scoped active memories, token-bounded.

NameTypeReqDescription
max_tokensinteger––
workspacestring––

No output schema declared.

No examples provided.

quarantine ~33

Move an entry to the quarantine lane (review hold).

NameTypeReqDescription
entry_idintegeryes–
reasonstring––

No output schema declared.

No examples provided.

recall ~48

Keyword-ranked recall over active memories only — quarantined and retracted entries never leak into context.

NameTypeReqDescription
limitinteger––
querystring––
tagsstring––
NameTypeReqDescription
resultarrayyes–

No examples provided.

release ~27

Human override: move a quarantined entry back to active.

NameTypeReqDescription
entry_idintegeryes–

No output schema declared.

No examples provided.

retain ~83

Screen and store a durable memory. The quarantine gate runs on every write — entries flagged secret:/injection:/limit:/shape: land in quarantine, never in recall. Returns the stored entry.

NameTypeReqDescription
contentstringyes–
source_rowid–––
source_sessionstring––
tagsstring––
workspacestring––

No output schema declared.

No examples provided.

retract ~27

Withdraw an entry — kept for history, never recalled again.

NameTypeReqDescription
entry_idintegeryes–

No output schema declared.

No examples provided.

screen ~48

Dry-run the anti-poisoning gate: returns the status retain would produce (active | quarantined + reasons) without writing.

NameTypeReqDescription
contentstringyes–
tagsstring––

No output schema declared.

No examples provided.

supersede ~41

Replace an entry with a corrected version (versioned).

NameTypeReqDescription
contentstringyes–
entry_idintegeryes–
tagsstring––

No output schema declared.

No examples provided.

verify ~37

Audit an entry's provenance against a Devin sessions.db (read-only).

NameTypeReqDescription
entry_idintegeryes–
sessions_dbstringyes–

No output schema declared.

No examples provided.

Install

How do I install the io.github.Icaro0310/devin-memory MCP server?

io.github.Icaro0310/devin-memory runs locally as a PyPI package, launched with uvx devin-memory-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 · devin-memory-mcp

# add to Claude Code
claude mcp add icaro0310-devin-memory -- uvx devin-memory-mcp
Common questions

What is the io.github.Icaro0310/devin-memory MCP server?

io.github.Icaro0310/devin-memory is an MCP server listed in the public MCP registry as io.github.Icaro0310/devin-memory. Anti-poisoning memory for agents: provenance, conflicts, quarantine gate. This page covers its PyPI package (devin-memory-mcp).

Is the io.github.Icaro0310/devin-memory MCP server safe to use?

io.github.Icaro0310/devin-memory scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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.Icaro0310/devin-memory MCP server expose?

io.github.Icaro0310/devin-memory exposes 13 tools: retain, recall, screen, list, retract, and 8 more. Their descriptions and schemas cost roughly 528 tokens of context every time the server is loaded.

Is the io.github.Icaro0310/devin-memory MCP server still maintained?

io.github.Icaro0310/devin-memory is still listed as active in the MCP registry. We last reached this channel on 4 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.Icaro0310/devin-memory MCP server under?

io.github.Icaro0310/devin-memory declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.