Skip to main content

fireweed-mcp

Agent memory where every fact carries a receipt.

remember(claim    = "Priya joined Acme in 2019 under duress.",
         evidence = "Priya Raman joined Acme in 2019 as a logistics analyst.")

REFUSED (asserts_more_than_evidence) — the claim adds something the evidence does not say.
  claim   : Priya joined Acme in 2019 under duress.
  evidence: Priya Raman joined Acme in 2019 as a logistics analyst.
recall("Priya's salary")

ABSTAINED (unknown_predicate) — no claims ground "salary"; 1 claim about Priya Raman exists
This is a refusal, not an empty result.
forget("Priya")

ERASED Priya Raman — certificate issued
  signature            : hmac-sha256:f4d0768ef3b0fec624afec12f25bfd91…
  nodes in closure     : 1
  every probe abstains : True
  bystanders surviving : 1

That last one is the artifact behind "delete me from your agent's memory — and prove it."

Install

uvx fireweed-mcp          # try it
pip install fireweed-mcp  # keep it
claude mcp add fireweed -- uvx fireweed-mcp

No dependencies. No API keys. No model — nothing in this server calls an LLM.

What it does

tool
remember admits a claim only if the evidence you cite supports it. Refusals are typed and say what to fix.
recall grounded claims with the byte range they came from; abstains and names the term it could not ground
verify_receipts re-hash every source, re-slice every range — tamper-evident
forget erasure with exact closure and a signed certificate; bystanders survive
export_memory the whole substrate as a portable open-format blob

Why the refusals are the point

Most memory servers store what the model says and return what's nearest. This one adjudicates.

The rule is the model proposes, deterministic code decides. Across an RPC boundary that stops being a slogan: your agent is the proposer, and it cannot talk its way past the gate, because the gate is not a prompt. Pass a claim and the text you're quoting; pure functions check that the evidence names the subject, preserves the relation, invents no numbers, and asserts nothing the span doesn't say. What survives is stored with a byte range into the source.

Then anyone can check it afterwards — including someone who trusts neither your agent nor this server. That is the whole product.

What it does NOT do

Stated up front, because this project's last headline number turned out to be measuring nothing (see the retraction, which ships with a script that proves it):

  • It does not extract memories from free text. You supply the claim and the evidence. Automatic extraction needs a perceiver model; this server deliberately has none.
  • It does not make an LLM truthful. It governs what enters the record and what can be proven about it. Your model can still say whatever it likes in its own prose.
  • Recall is weak, and measured on both axes. On questions whose answer is genuinely absent, the gate abstains on only 38% — it checks that the question's topic is grounded, not that the asked-for value exists. On a paired corpus of questions the stored facts do answer, it returns the right answer 24% of the time against 75% for plain retrieval-and-read. Both numbers come from a calibrated instrument that prints its own controls before measuring; the method and the failures behind it are written up in the private repo's evaluation notes. The write path, receipts and erasure are unaffected and are the parts to rely on.

Your data

~/.fireweed/mcp/ (FIREWEED_MCP_STORE to change). The substrate is an open format — see open_format/SPEC.md — and open_format/reference_reader.py reads it with the standard library alone. Your memory outlives this server, this engine, and any model. A test asserts that round trip.

Optional: pip install "fireweed-mcp[semantic]" enables paraphrase matching in recall. Without it the gate refuses more — the safe direction — and memory_stats tells you which mode you're in.

License

FSL-1.1-ALv2 — source-available. Free for everything except building a competing product; converts to Apache 2.0 on 2028-01-01. Full text in LICENSE.md.

Want to use Fireweed in a commercial product or competing service? → sanyamsood2@gmail.com

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

fireweed_mcp-0.1.3.tar.gz (143.0 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

fireweed_mcp-0.1.3-py3-none-any.whl (152.6 kB view details)

Uploaded Python 3

File details

Details for the file fireweed_mcp-0.1.3.tar.gz.

File metadata

  • Download URL: fireweed_mcp-0.1.3.tar.gz
  • Upload date:
  • Size: 143.0 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for fireweed_mcp-0.1.3.tar.gz
Algorithm Hash digest
SHA256 eda49d23ed3ba5a8178f7d59008859188fc43d0fefc1e91c0b76a94853c664ae
MD5 661c85ca90b9c46f6d03ea9a7534eaee
BLAKE2b-256 db77a321f4be28a9017c58abd5e0bcafc27da5b18e558e78a23977e1daa2be7c

See more details on using hashes here.

Provenance

The following attestation bundles were made for fireweed_mcp-0.1.3.tar.gz:

Publisher: publish.yml on Starksood/fireweed-mcp

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file fireweed_mcp-0.1.3-py3-none-any.whl.

File metadata

  • Download URL: fireweed_mcp-0.1.3-py3-none-any.whl
  • Upload date:
  • Size: 152.6 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for fireweed_mcp-0.1.3-py3-none-any.whl
Algorithm Hash digest
SHA256 d35a6c83a75fb3d5ebea4b5e0011a212483e918328a6687fc5a3ef246ef2a9e2
MD5 09f6a2c9b6f25905bad1f52d8e1af239
BLAKE2b-256 3ea848ad8a93d3322c2a93e38568ec654fc25c6555f0ba779cf3f695acc8885b

See more details on using hashes here.

Provenance

The following attestation bundles were made for fireweed_mcp-0.1.3-py3-none-any.whl:

Publisher: publish.yml on Starksood/fireweed-mcp

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Release history Release notifications | RSS feed

0.1.4

2 files

This release

0.1.3 This release

2 files

0.1.2

2 files

0.1.1

2 files

0.1.0

2 files

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page