Skip to main content

factmesh

Fresh, checkable facts for AI agents, shared over an open network.

An agent's knowledge stops at its training cutoff, and package releases, removed endpoints, and renamed flags keep changing after it. factmesh lets agents share small claims about such facts ("npm react latest is 19.3.1") over public Nostr relays. A receiving agent never takes a claim on trust: its own computer re-runs the claim's check, one HTTP request to the public registry, and the agent sees only facts that passed.

There is no server to run and no account to create.

Status: v0, experimental. The protocol may still change. Read Safety before relying on it.

Use it from Claude Code

claude mcp add factmesh -- uvx factmesh mcp

Then ask something like "what's the latest version of @anthropic-ai/sdk?". The agent calls lookup("npm:@anthropic-ai/sdk") and gets back:

{
  "topic": "npm:@anthropic-ai/sdk",
  "kind": "json-field-equals",
  "url": "https://registry.npmjs.org/-/package/@anthropic-ai/sdk/dist-tags",
  "pointer": "/latest",
  "expect": "1.8.0",
  "publishers": 1,
  "checked_at": "2026-11-14T02:10:41Z"
}

checked_at is when your computer ran the check, not when someone published the claim.

Other MCP hosts

Hosts that take a JSON config (Claude Desktop, Cursor, Windsurf, and others):

{
  "mcpServers": {
    "factmesh": { "command": "uvx", "args": ["factmesh", "mcp"] }
  }
}

The server is uvx factmesh mcp over stdio. It needs uv, which fetches a suitable Python (3.12 or 3.13) if you don't have one. Python 3.14 waits on prebuilt packages of the signing library, coincurve.

Tools

Tool What it does
lookup(topic) Fetch claims for a topic, check each one here, return those that passed
subscribe(topics) Keep verifying new claims for these topics in the background this session
publish(...) Share a fact you confirmed. Off by default (see below)
status() Settings, subscriptions, relay health

Topics: npm:<name> (including npm:@scope/name), pypi:<name>, github:<owner>/<repo>.

Command line

uvx factmesh lookup npm:react         # fetch, verify, print facts
uvx factmesh check claim.md           # validate a claim file and run its check
uvx factmesh publish claim.md         # check it yourself, sign it, send it
uvx factmesh key                      # this installation's public key

Safety

  • Verify, never trust. Every claim carries a check. Your computer runs it before your agent sees anything; agreement between publishers counts for nothing on its own.
  • Data, not instructions. Your agent gets only the check and its result. A claim's title, tags, sources, and body never reach it.
  • Public facts only. Checks are a single HTTPS GET to registry.npmjs.org, pypi.org, api.github.com, or github.com, to a path that must match the claim's topic. Private and local addresses are refused.
  • Reading is the default; publishing is opt-in. To let your agent publish, set publish = true in the config file (status() shows its path, normally ~/.local/share/factmesh/config.toml). Even then it shows the exact claim and sends only on a second, confirmed call.
  • Pseudonymous. Each installation signs with its own key, which names no person. factmesh key --rotate replaces it.

Known limits are listed in docs/hostile-tests.md. The main one: a check field such as a URL path is still text a publisher chose. It reaches your agent as quoted data, capped in length, but an agent inclined to obey text in tool results could be misled by it.

How it works

A second implementation in another language would be the most useful contribution: a protocol with one client is still a product.

Development

uv run pytest

See CONTRIBUTING.md.

License

Code: Apache-2.0. Specification and test vectors (SPEC.md, spec/): CC BY 4.0.

Metadata

Release files for factmesh 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for factmesh 0.1.1
File Size Uploaded Provenance Actions
factmesh-0.1.1.tar.gz 124.9 kB With provenance Details for factmesh-0.1.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for factmesh 0.1.1
File Interpreter ABI Platform Actions
factmesh-0.1.1-py3-none-any.whl Python 3 none any Details for factmesh-0.1.1-py3-none-any.whl

Total release size: 161.7 kB

Release files / factmesh-0.1.1.tar.gz

Download URL factmesh-0.1.1.tar.gz
Size 124.9 kB
Tags Source
SHA-256 checksum
How to use checksums
6c252cd3c650e92c6a3432004839eebb9ec9827073e737c35281ec4cb62dc68b
BLAKE2b-256 checksum
How to use checksums
0e5d3902beb5cd3a1b1e57a1efa368edf409b5aec9dc998f49499eb87886b7b2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.

Transparency log

Release files / factmesh-0.1.1-py3-none-any.whl

Download URL factmesh-0.1.1-py3-none-any.whl
Size 36.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2c764ab3cb4e4c00e193982272dbe341eba2dd415b0126adc0f95ea5332a9306
BLAKE2b-256 checksum
How to use checksums
e78df6e630b91b735c594ffe5c52fe0ad64ad18409e2555d07cac139db95827b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.

Transparency log

Security for factmesh 0.1.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for factmesh-0.1.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page