aafp-commons
The server exposes a local, signed knowledge ledger for agent packets, with read operations plus policy-gated proposal admission.
commons_world: Read the local signed world; safe in source posture.commons_query: Query exact packet IDs or scan namespace prefixes; an empty query scans all admitted namespaces (commons/,org/,agent/).commons_get: Read one signed packet by content address (packet_id).commons_assume_constitution: Validate the constitution selected bycommons init; admission is explicit and evidence-gated.commons_propose: Sign and admit a packet; requires subject posture, evidence, and an installed digest-pinned constitution.commons_conflicts: Read conflict IDs in the local world.commons_resolutions: Read resolution IDs in the local world.Read operations do not require network access; writing requires initialized subject posture and policy/evidence checks.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@aafp-commons what's the current world posture?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Frozen as of 2026-10-16. Not the live trust surface. trustcard is. This ledger stays as a record; no further protocol work is planned.
AAFP Commons
AAFP Commons is a local signed knowledge notebook for software agents. Packets carry claims, evidence, methods, constitution references, and Ironclad signatures. Admission is policy-gated and objects are content-addressed.
Identity, signing authority, constitution, provenance, and reputation are separate concerns. The local ledger records immutable packet admissions; it is not a shared mutable database or a replacement for AAFP transport.
Operator and agent handbook: docs/HANDBOOK.md. Evidence, constitutions, and
review: docs/EVIDENCE.md, docs/CONSTITUTIONS.md, docs/REVIEW.md.
Real-workload preflight: docs/REAL-WORKLOAD.md.
Quick start
export COMMONS_HOME=/tmp/commons-demo
commons init
commons world
commons mcpIf the commons console script is not installed, use:
uv run --no-sync python -m aafp_commons mcpBefore writing, an agent should call commons_world and inspect posture.
Source posture is read-only. commons init creates the local signing subject
and installs the selected built-in constitution; it does not prove a claim.
Empty commons_query scans every admitted namespace (commons/, org/,
and agent/), not only commons/.
Related MCP server: Living Stack MCP — Retired Beta Listing
MCP surface
The zero-configuration stdio server exposes:
commons_world, commons_query, commons_get,
commons_assume_constitution, commons_propose, commons_conflicts, and
commons_resolutions.
Proposals require evidence and a digest-pinned constitution. Read operations
do not require network access. commons serve binds loopback at
127.0.0.1:8081 by default and exposes the frozen /world object plus the
minimum loopback packet pull used for two-home replication.
Development
uv run --no-sync pytest -q
uv run --no-project ruff check src testsThe sibling local Ironclad checkout is used by uv in this development tree.
No registry, hosted service, or external node is required for the local tests.
Packaging
uv build produces a source distribution and a universal wheel from this tree:
uv buildArtifacts land in dist/:
aafp_commons-0.1.0.tar.gz— source distributionaafp_commons-0.1.0-py3-none-any.whl— wheel (bundlesprotocols/andconstitutions/viaforce-include)
Install the built wheel directly from source without any registry:
uv pip install dist/aafp_commons-0.1.0-py3-none-any.whlNo publish, registry upload, or external index is required.
Available Tools
7 toolscommons_assume_constitutionA
Validate the constitution selected by commons init. Constitution admission is explicit and evidence-gated; source posture must run commons init first.
Inputs: no named parameters.
commons_conflictsB
Read conflict IDs in the local world. Evidence and constitution rules apply to any future proposal that creates conflict objects.
Inputs: no named parameters.
commons_getA
Read one signed packet by content address. Writing requires evidence and a digest-pinned constitution.
Inputs: packet_id (required).
commons_proposeB
Sign and admit one packet. Subject posture, at least one evidence reference, and an installed digest-pinned constitution are required.
Inputs: claim (required), evidence (required), namespace (required), kind, +7 more.
commons_queryA
Query exact packet IDs or scan a namespace prefix. An empty query scans every admitted namespace (commons/, org/, and agent/). Results are signed packets; proposals still require evidence and a digest-pinned constitution.
Inputs: query.
commons_resolutionsB
Read resolution IDs in the local world. Evidence and constitution rules apply to any future resolution proposal.
Inputs: no named parameters.
commons_worldA
Read the local signed world. This is safe in source posture; writing requires an initialized subject, evidence, and a digest-pinned constitution.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
The read tools are separated by scope: world reads the whole signed world, query searches by packet ID or namespace, and get retrieves one content-addressed packet. Conflicts and resolutions are clearly distinct read endpoints, though query and get could still cause minor selection hesitation.
All tools share the commons_ prefix, which establishes a strong family identity. However, suffixes mix nouns like world, conflicts, and resolutions with verbs like query, get, and propose, so the set is readable but not a uniform verb_noun convention.
Seven tools is well-scoped for a signed-packet commons governance domain. Each tool has a distinct role without redundant operations.
Core read, query, propose, and conflict/resolution read operations are covered. However, prerequisites such as commons init, evidence management, and constitution setup or updates have no MCP-visible tools, leaving meaningful gaps in the write/propose workflow.
Maintenance
Related MCP Connectors
Tamper-evident proof creation and verification for AI agents via MCP, A2A, and REST.
Governed personal world model and memory for your AI agent. Pair once, connect over MCP.
Host any HTTP API as MCP tools with a tamper-evident cross-agent settlement ledger.
Persistent, inspectable memory for AI agents with lineage, correction, and a hosted MCP endpoint.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceProvides evidence-oriented MCP service for cryptographically identified agents, bounded public contracts, privacy-preserving records, and append-only audit.Apache 2.0
- AlicenseAqualityBmaintenanceRetired snapshot of the former 15-tool Apache-2.0 beta. Use Living Stack Community for the free seven-tool proof edition; Complete Local is the paid runtime with memory, recovery, signed traces, release verification, and multi-agent workflows.14Apache 2.0
- AlicenseAqualityBmaintenanceFree seven-tool proof loop for MCP agents: scoped sessions, bounded authorization, typed outcomes, evidence-bound claims, and tamper-evident local closure. Upgrade to Complete Local for durable memory, recovery, signed traces, release verification, and multi-agent workflows.7Apache 2.0

argmem-mcpofficial
AlicenseNot gradedqualityCmaintenanceEnables LLM agents and MCP clients to build an argumentation-based memory store where grounded observations support claims, objections contest them, and beliefs are computed as held, contested, lapsed, or retracted, all persisted in an append-only audit log that replays to identical state. Ships as a stdio launcher that starts the proprietary local engine for use with Claude, Claude Code, Cursor, and other MCP clients.12 npmMIT