# Homestead Memory (pypi · homestead-memory)

Tamper-evident record of what your AI agent did, plus local-first verifiable memory.

- Trust score: 80/100 (high trust)
- Change this week: +19
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- pypi · `homestead-memory`: 80/100 (this document), [markdown](https://verifymcp.io/servers/fuckbigtech-ai-homestead-memory/homestead-memory.md), [page](https://verifymcp.io/servers/fuckbigtech-ai-homestead-memory/homestead-memory)

## Channel facts

- Registry: `pypi`
- Package: `homestead-memory`
- Version: `0.5.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it.
  - 0 of 4 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 524 tokens (~58/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 57% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add fuckbigtech-ai-homestead-memory -- uvx homestead-memory
```

### Cursor

```json
{
  "mcpServers": {
    "fuckbigtech-ai-homestead-memory": {
      "command": "uvx",
      "args": [
        "homestead-memory"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "fuckbigtech-ai-homestead-memory": {
      "command": "uvx",
      "args": [
        "homestead-memory"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add fuckbigtech-ai-homestead-memory -- uvx homestead-memory
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fuckbigtech-ai-homestead-memory": {
      "type": "local",
      "command": [
        "uvx",
        "homestead-memory"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fuckbigtech-ai-homestead-memory --command uvx --arg homestead-memory
```

### Hermes

```yaml
mcp_servers:
  fuckbigtech-ai-homestead-memory:
    command: "uvx"
    args: ["homestead-memory"]
```

### Netclaw

```json
{
  "McpServers": {
    "fuckbigtech-ai-homestead-memory": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "homestead-memory"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add fuckbigtech-ai-homestead-memory -t stdio -c uvx -a homestead-memory
```

### Other

```json
{
  "mcpServers": {
    "fuckbigtech-ai-homestead-memory": {
      "command": "uvx",
      "args": [
        "homestead-memory"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 80, +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.

### 2026-09-19 (score 79, +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.

### 2026-09-17 (score 78, +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.

### 2026-09-15 (score 77, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-14 (score 61, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-12 (score 76, +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.

### 2026-09-11 (score 75, +7)

- [security regression] Stability: 0.50 → unverified
- [security regression] Tool safety: pass → unverified
- [security improvement] Install scripts: unverified → pass
- [security] The scripts that run when this package is installed changed: build_backend
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] MCP protocol: fail → pass
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.4.0 → 0.5.0

### 2026-09-10 (score 68, +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.

## MCP tools (9)

### `memory_ask` (~69 tokens)

Ask the memory a question: retrieve the most relevant notes (and synthesize an answer if a reader is configured via HSM_READER).

Input parameters:

- `k` (integer): number of passages
- `query` (string, required)
- `type` (string): question type (default: auto-classified)

### `memory_search` (~40 tokens)

Search the memory: ranked passages (title, path, score, snippet).

Input parameters:

- `k` (integer): number of passages
- `query` (string, required)

### `memory_verify` (~66 tokens)

Run the memory-integrity gate (RotBench): score /100 plus every failure/warning. Read-only.

Input parameters:

- `deep` (boolean): also run retrieval-resilience/fixtures/freshness checks
- `signer` (string): trusted Ed25519 public key required for signature provenance checks

### `memory_history` (~55 tokens)

A note's recorded change history from its Changelog (temporal layer).

Input parameters:

- `as_of` (string): YYYY-MM-DD: what was recorded on/before this date
- `note` (string, required): note stem or relative path

### `memory_ingest` (~43 tokens)

MUTATES local state: (re)build the search index (qmd) and the temporal sidecar for the vault. Can take a while on large vaults.

### `memory_sign` (~46 tokens)

MUTATES local state: sign the vault's canonical markdown state with a local Ed25519 key. Requires homestead-memory[sign].

Input parameters:

- `key` (string): private seed path override

### `memory_distill` (~52 tokens)

MUTATES local state unless dry=true: run the write-time distilled layer (extract cited entity facts from new/changed notes).

Input parameters:

- `agent` (string): writer identity for provenance
- `dry` (boolean)

### `memory_remember` (~62 tokens)

MUTATES local state: directly write one provenance-stamped distilled fact.

Input parameters:

- `agent` (string): writer identity for provenance
- `entity` (string, required)
- `field` (string, required)
- `source` (string)
- `value` (string, required)

### `memory_resolve` (~64 tokens)

MUTATES local state: resolve duplicate-value conflicts in one distilled note, preserving the historical changelog.

Input parameters:

- `agent` (string): resolver identity for provenance
- `entity` (string, required)
- `field` (string)
- `strategy` (string): default: latest

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/fuckbigtech-ai-homestead-memory/homestead-memory#diagnostics

## Score history

- 2026-09-21: 80
- 2026-09-20: 79
- 2026-09-19: 79
- 2026-09-18: 78
- 2026-09-17: 78
- 2026-09-16: 77
- 2026-09-15: 77
- 2026-09-14: 61
- 2026-09-13: 76
- 2026-09-12: 76
- 2026-09-11: 75
- 2026-09-10: 68
- 2026-09-09: 67
- 2026-09-08: 67
- 2026-09-07: 66
- 2026-09-06: 66
- 2026-09-05: 65
- 2026-09-04: 65
- 2026-09-03: 64
- 2026-09-02: 64
- 2026-09-01: 63
- 2026-08-31: 63
- 2026-08-30: 61
- 2026-08-29: 61
- 2026-08-28: 61
- 2026-08-27: 61
- 2026-08-26: 46

## Common questions

### 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 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 21 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.

## Links

- PyPI project: https://pypi.org/project/homestead-memory/
- Socket report: https://socket.dev/pypi/package/homestead-memory
- Repository: https://github.com/fuckbigtech-ai/homestead-memory
- Website: https://fuckbigtech.ai/lab/
- Changelog RSS feed: https://verifymcp.io/servers/fuckbigtech-ai-homestead-memory/homestead-memory.xml
- Changelog JSON feed: https://verifymcp.io/servers/fuckbigtech-ai-homestead-memory/homestead-memory.json
- HTML version of this page: https://verifymcp.io/servers/fuckbigtech-ai-homestead-memory/homestead-memory