io.github.michael-denyer/hot-memory-mcp
PYPI · HOT-MEMORY-MCP
Two-tier memory: hot cache (0ms) + semantic search. Self-organizing.
Available components
Last scanned (5 hours ago)
Scores higher than 62% of PyPI 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 Security49
- Malware scan not yet available for this package.Unverified
- Known CVEs were checked across the 107 of 108 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- Dependency health was assessed across the 107 of 108 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to michael-denyer/memory-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 126 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 4902 tokens (~83/item across 59 items; 56 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 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
- Structured output schemas are declared (100% 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 3 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 57 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 −15
- Malware scan: pass → unverified ▼ security
- 4 Nov 26 +32
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.00 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 13 Oct 26 +11
- Known CVEs: unverified → partial ▲ security
- Dependency health: unverified → partial ▲ functional
- 12 Oct 26 −11
- Known CVEs: partial → unverified ▼ security
- Dependency health: partial → unverified ▼ functional
- 3 Oct 26 −10
- Malware scan: pass → unverified ▼ security
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 pypi/hot-memory-mcp@0.8.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | michael-denyer/memory-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/michael-denyer/memory-mcp/.github/workflows/publish.yml@refs/tags/v0.8.0 |
| Rekor log index | 2043462112 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:f1d2585d4c3316d06f94bf8f369f645d2c8306f0f24a81fa82cfa1179cf97a03 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 107 packages
| Packages resolved | 107 |
|---|---|
| Stale | 5 |
| No linked repository | 1 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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 →
summarize_session ~124
Summarize a session's key decisions, insights, and action items. Groups session memories by semantic category to extract structured knowledge: - Decisions: Choices made and their rationale - Insights: Lessons learned, antipatterns, landmines, constraints - Action Items: TODOs, bugs, tasks to complete - Context: Background info, conventions, preferences, architecture Use this before end_session() to review what was captured, or anytime to get a structured view of a conversation's key takeaways.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | Session ID to summarize |
Structured output declared, but exposes no named fields.
No examples provided.
unlink_memories ~82
Remove relationship(s) between two memories. If relation_type is specified, only removes that specific relationship. If not specified, removes all relationships between the two memories.
| Name | Type | Req | Description |
|---|---|---|---|
| from_memory_id | integer | yes | Source memory ID |
| relation_type | – | – | Specific relation type to remove, or None to remove all |
| to_memory_id | integer | yes | Target memory ID |
Structured output declared, but exposes no named fields.
No examples provided.
unpin ~39
Unpin a memory, making it eligible for auto-eviction from hot cache.
| Name | Type | Req | Description |
|---|---|---|---|
| memory_id | integer | yes | ID of memory to unpin |
Structured output declared, but exposes no named fields.
No examples provided.
validate_embeddings ~53
Check if the embedding model has changed since database was created. If the model or dimension has changed, existing embeddings may be incompatible and memories may need re-embedding. Returns validation status and details about any mismatches.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
validate_memory ~204
Mark a memory as validated/confirmed useful. Increases the memory's trust score and records the reason in the trust history. Use this when you verify that a recalled memory is still accurate and helpful. Reasons and their default boosts: - used_correctly: +0.05 (memory was applied successfully) - explicitly_confirmed: +0.15 (user explicitly confirmed accuracy) - cross_validated: +0.20 (corroborated by multiple sources) Trust score is capped at 1.0.
| Name | Type | Req | Description |
|---|---|---|---|
| boost | – | – | Custom trust boost (overrides reason default). If None, uses reason's default. |
| memory_id | integer | yes | ID of memory to validate |
| note | – | – | Optional note explaining the validation context |
| reason | – | – | Reason for validation: 'used_correctly' (applied and worked), 'explicitly_confirmed' (user verified), 'cross_validated' (multiple sources agree). If not specified, uses default boost. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
warm_cache ~64
Pre-warm hot cache with predicted next memories. Promotes predicted memories to hot cache for instant recall. Only promotes memories that aren't already in hot cache. Requires MEMORY_MCP_PREDICTIVE_CACHE_ENABLED=true.
| Name | Type | Req | Description |
|---|---|---|---|
| memory_id | integer | yes | Memory ID to predict from |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.michael-denyer/hot-memory-mcp server?
io.github.michael-denyer/hot-memory-mcp runs locally as a PyPI package, launched with uvx hot-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 · hot-memory-mcp
claude mcp add michael-denyer-hot-memory-mcp -- uvx hot-memory-mcp
What is the io.github.michael-denyer/hot-memory-mcp server?
io.github.michael-denyer/hot-memory-mcp is listed in the public MCP registry as io.github.michael-denyer/hot-memory-mcp. Two-tier memory: hot cache (0ms) + semantic search. Self-organizing. This page covers its PyPI package (hot-memory-mcp).
Is the io.github.michael-denyer/hot-memory-mcp server safe to use?
io.github.michael-denyer/hot-memory-mcp scores 66 out of 100 on VerifyMCP. Its build provenance is signed and verified. 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.michael-denyer/hot-memory-mcp server expose?
io.github.michael-denyer/hot-memory-mcp exposes 56 tools: remember, recall, recall_with_fallback, recall_by_tag, forget, and 51 more. Their descriptions and schemas cost roughly 4,615 tokens of context every time the server is loaded.
Is the io.github.michael-denyer/hot-memory-mcp server still maintained?
io.github.michael-denyer/hot-memory-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.michael-denyer/hot-memory-mcp server under?
io.github.michael-denyer/hot-memory-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.