feedback-memory
MCPB · FEEDBACK-MEMORY.MCPB
Remembers why you approved, edited or rejected your agent's drafts; recalls the closest corrections
Available components
Last scanned (7 hours ago)
Scores higher than 89% of MCPB 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 Security23
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 94 of 94 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 31 of 94 dependencies flagged as unhealthy. 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 15 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 413 tokens (~82/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "forget" implies "delete" 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 5 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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +5
- Stability: unverified → 0.37 ▲ functional
- 2 Oct 26 45
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 17 Oct 2026 · Analysed mcpb/https://github.com/ssap-pa/self-learning-agent-setup/releases/download/v0.2.1/feedback-memory.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 31 |
| 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 →
add_rule Save a standing rule ~63
When the user states a preference that should ALWAYS apply ("never use exclamation marks", "prices only from the database"), save it as a rule. Rules come back first in every recall_corrections.
| Name | Type | Req | Description |
|---|---|---|---|
| rule | string | yes | The rule, as one short sentence |
No output schema declared.
No examples provided.
forget Delete a rule or a decision ~45
Delete one rule or one stored decision by id (ids come from list_memory). Use when the user says a rule or a past correction no longer applies.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
list_memory Show what's stored ~66
Show the active rules, the most recent decisions with their ids, and how many approve / edit / reject decisions were stored in the last 7 days. Use it when the user asks what you remember, or to check that decisions are actually being stored.
| Name | Type | Req | Description |
|---|---|---|---|
| recent | integer | – | – |
No output schema declared.
No examples provided.
recall_corrections Recall the user's rules and past corrections ~105
Call this BEFORE you draft anything the user will review (posts, replies, emails, docs, commit messages, UI copy, code in a style they care about). Returns the user's standing rules and their past approve / edit / reject decisions on similar tasks, most similar first. Follow them.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| task | string | yes | What you are about to do, in one or two sentences (include the request or the text you are replying to) |
No output schema declared.
No examples provided.
record_decision Record the user's approve / edit / reject ~134
Call this right AFTER the user approves, edits or rejects something you drafted. Pass the user's reason in one line when they give one: the reason is what makes the next draft better. For an edit, pass the final text the user wanted.
| Name | Type | Req | Description |
|---|---|---|---|
| corrected_text | string | – | For edits: the final text the user wanted |
| decision | string | yes | – |
| draft | string | – | What you had drafted |
| reason | string | – | The user's reason, one line, in their words |
| task | string | yes | The task the draft was for (same wording you would pass to recall_corrections) |
No output schema declared.
No examples provided.
How do I install the feedback-memory MCP server?
feedback-memory ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, f2625e11c8f95f45246b365aaa3d8609111e1e22d1d6a3ad7987136e7d9515a8; the commands to do that are on this page. If it does not match, do not open it.
mcpb · feedback-memory.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
f2625e11c8f95f45246b365aaa3d8609111e1e22d1d6a3ad7987136e7d9515a8
macOS / Linux
echo "f2625e11c8f95f45246b365aaa3d8609111e1e22d1d6a3ad7987136e7d9515a8 feedback-memory.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\feedback-memory.mcpb).Hash -eq "f2625e11c8f95f45246b365aaa3d8609111e1e22d1d6a3ad7987136e7d9515a8"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the feedback-memory MCP server?
feedback-memory is an MCP server listed in the public MCP registry as io.github.ssap-pa/feedback-memory. Remembers why you approved, edited or rejected your agent's drafts; recalls the closest corrections. This page covers its MCPB bundle (https://github.com/ssap-pa/self-learning-agent-setup/releases/download/v0.2.1/feedback-memory.mcpb).
Is the feedback-memory MCP server safe to use?
feedback-memory scores 52 out of 100 on VerifyMCP. 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 feedback-memory MCP server expose?
feedback-memory exposes 5 tools: recall_corrections, record_decision, add_rule, list_memory, forget. Their descriptions and schemas cost roughly 413 tokens of context every time the server is loaded.
What licence is the feedback-memory MCP server under?
feedback-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.