Homestead Memory
PYPI · HOMESTEAD-MEMORY · SCANNED SEP 20
Tamper-evident record of what your AI agent did, plus local-first verifiable memory.
Available components
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 Security100
- 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 native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- 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 8 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 524 tokens (~58/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
How do I install the Homestead Memory MCP server?
Homestead Memory runs locally as a PyPI package, launched with uvx homestead-memory. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · homestead-memory
claude mcp add fuckbigtech-ai-homestead-memory -- uvx homestead-memory
{
"mcpServers": {
"fuckbigtech-ai-homestead-memory": {
"command": "uvx",
"args": [
"homestead-memory"
]
}
}
} {
"servers": {
"fuckbigtech-ai-homestead-memory": {
"command": "uvx",
"args": [
"homestead-memory"
]
}
}
} codex mcp add fuckbigtech-ai-homestead-memory -- uvx homestead-memory
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fuckbigtech-ai-homestead-memory": {
"type": "local",
"command": [
"uvx",
"homestead-memory"
],
"enabled": true
}
}
} openclaw mcp add fuckbigtech-ai-homestead-memory --command uvx --arg homestead-memory
mcp_servers:
fuckbigtech-ai-homestead-memory:
command: "uvx"
args: ["homestead-memory"] {
"McpServers": {
"fuckbigtech-ai-homestead-memory": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"homestead-memory"
]
}
}
} assistant mcp add fuckbigtech-ai-homestead-memory -t stdio -c uvx -a homestead-memory
{
"mcpServers": {
"fuckbigtech-ai-homestead-memory": {
"command": "uvx",
"args": [
"homestead-memory"
]
}
}
} 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 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.
- 17 Sept 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.
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +7
- Stability: 0.50 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Install scripts: unverified → pass ▲ security
- The scripts that run when this package is installed changed: build_backend security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- MCP protocol: fail → pass ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.4.0 → 0.5.0 functional
- 10 Sept 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.
- 8 Sept 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.
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/homestead-memory@0.5.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 | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 4 packages
| Packages resolved | 4 |
|---|---|
| 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 →
memory_ask ~69
Ask the memory a question: retrieve the most relevant notes (and synthesize an answer if a reader is configured via HSM_READER).
| Name | Type | Req | Description |
|---|---|---|---|
| k | integer | – | number of passages |
| query | string | yes | – |
| type | string | – | question type (default: auto-classified) |
No output schema declared.
No examples provided.
memory_distill ~52
MUTATES local state unless dry=true: run the write-time distilled layer (extract cited entity facts from new/changed notes).
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | writer identity for provenance |
| dry | boolean | – | – |
No output schema declared.
No examples provided.
memory_history ~55
A note's recorded change history from its Changelog (temporal layer).
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | YYYY-MM-DD: what was recorded on/before this date |
| note | string | yes | note stem or relative path |
No output schema declared.
No examples provided.
memory_ingest ~43
MUTATES local state: (re)build the search index (qmd) and the temporal sidecar for the vault. Can take a while on large vaults.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
memory_remember ~62
MUTATES local state: directly write one provenance-stamped distilled fact.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | writer identity for provenance |
| entity | string | yes | – |
| field | string | yes | – |
| source | string | – | – |
| value | string | yes | – |
No output schema declared.
No examples provided.
memory_resolve ~64
MUTATES local state: resolve duplicate-value conflicts in one distilled note, preserving the historical changelog.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | resolver identity for provenance |
| entity | string | yes | – |
| field | string | – | – |
| strategy | string | – | default: latest |
No output schema declared.
No examples provided.
memory_search ~40
Search the memory: ranked passages (title, path, score, snippet).
| Name | Type | Req | Description |
|---|---|---|---|
| k | integer | – | number of passages |
| query | string | yes | – |
No output schema declared.
No examples provided.
memory_sign ~46
MUTATES local state: sign the vault's canonical markdown state with a local Ed25519 key. Requires homestead-memory[sign].
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | – | private seed path override |
No output schema declared.
No examples provided.
memory_verify ~66
Run the memory-integrity gate (RotBench): score /100 plus every failure/warning. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| deep | boolean | – | also run retrieval-resilience/fixtures/freshness checks |
| signer | string | – | trusted Ed25519 public key required for signature provenance checks |
No output schema declared.
No examples provided.
What is the Homestead Memory MCP server?
Homestead Memory is an MCP server listed in the public MCP registry as io.github.fuckbigtech-ai/homestead-memory. Tamper-evident record of what your AI agent did, plus local-first verifiable memory. This page covers its PyPI package (homestead-memory).
Is the Homestead Memory MCP server safe to use?
Homestead Memory scores 79 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 Homestead Memory MCP server expose?
Homestead Memory exposes 9 tools: memory_ask, memory_search, memory_verify, memory_history, memory_ingest, and 4 more. Their descriptions and schemas cost roughly 497 tokens of context every time the server is loaded.
Is the Homestead Memory MCP server still maintained?
Homestead Memory 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.
What licence is the Homestead Memory MCP server under?
Homestead 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.