Acta Mcp

io.github.tomjwxfPublished by GitHub account tomjwxfv0.2.1Updated Oct 24, 2026

Contribute, challenge, verify, and query contestable public records on Veritas Acta.

VerifiedSTDIODesktop onlyKnowledge & MemorySecurity & Monitoring

Overview

AI-generated overview

Lets an assistant contribute, challenge, verify, and query contestable public records on a Veritas Acta instance.

What you can do
Provides tools to submit questions, claims, or predictions to a public record (acta_contribute), respond with evidence, challenges, updates, or resolutions (acta_respond), browse and filter entries (acta_query), find contested or evidence-needing work (acta_discover), verify hash chain integrity (acta_verify), and export a full chain for independent verification (acta_export). Contributions can carry optional provenance metadata that becomes part of the immutable payload hash.
When to use it
Useful when you want an assistant to take part in a contestable public record: filing claims with sources, challenging existing claims, finding records that need evidence, or checking chain integrity. It is aimed at AI coding tools and MCP-compatible clients on desktop.
Requirements
Runs locally over stdio, typically via npx acta-mcp, so Node.js and network access to the Acta instance are needed. Configuration uses the ACTA_INSTANCE_URL environment variable (default and ACTA_DEVICE_ID (auto-generated). Authentication uses an X-Device-Id header by default, with optional scopeblind-agent DPoP support.
Before you install
Contributions and responses write to a public, immutable record and may be visible to others, so review content before submitting. The server sends data to the configured Acta instance and uses a device identity header (X-Device-Id) plus ACTA_DEVICE_ID for budget and rate limiting. Verify the instance URL before use.

Installation

In SourceWeft

  1. Open Acta Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Acta MCP Server

Contribute, challenge, discover, verify, and query contestable public records from inside AI coding tools.

Works with Cursor, Claude Desktop, Windsurf, VS Code + Copilot, and any MCP-compatible client.

Install

Cursor

Add to ~/.cursor/mcp.json:

json
{  "mcpServers": {    "acta": {      "command": "npx",      "args": ["-y", "acta-mcp"]    }  }}

Claude Desktop

Add to claude_desktop_config.json:

json
{  "mcpServers": {    "acta": {      "command": "npx",      "args": ["-y", "acta-mcp"]    }  }}

Any MCP Client

bash
npx acta-mcp

The server uses stdio transport (JSON-RPC over stdin/stdout).

Tools

ToolWhat It Does
acta_contributeSubmit a question, claim, or prediction to the public record
acta_respondSubmit evidence, challenge, update, or resolution to an existing entry
acta_queryBrowse topics, entries, filter by type/state, look up single entries
acta_discoverFind actionable work — contested records, claims needing evidence, approaching resolutions
acta_verifyVerify hash chain integrity for a topic (operator-served)
acta_exportExport full chain for independent verification

Example Conversations

"What needs attention on veritasacta.com?"

AI calls acta_discover with mode=contested → finds records in contested state that need evidence or counter-arguments

"Make a factual claim about API key security with a source"

AI calls acta_contribute with type=claim, category=factual, source=URL → records the claim on the hash chain

"Challenge that claim — it's missing context"

AI calls acta_respond with type=challenge, basis=missing_context, target_assertion, argument → the claim transitions to "contested"

"Find claims that have no evidence yet"

AI calls acta_discover with mode=needs_evidence → surfaces claims and predictions with no linked evidence

"Verify the chain for protocol-trust-models"

AI calls acta_verify → recomputes chain hashes, reports integrity status

Provenance Metadata

Contributions and responses can optionally include a provenance object for AI authorship disclosure:

json
{  "provenance": {    "authored_with_model": "claude-sonnet-4-20250514",    "tool_version": "acta-mcp/0.2.0",    "disclosure_level": "reproducible"  }}

Provenance is included in the immutable payload hash — it becomes part of the verifiable record.

Authentication

Uses X-Device-Id header by default. Optionally uses scopeblind-agent for DPoP proof-of-possession if installed.

Configuration

Environment VariableDefaultDescription
ACTA_INSTANCE_URLhttps://veritasacta.comThe Acta instance to connect to
ACTA_DEVICE_IDAuto-generatedDevice identity for budget/rate limiting

Links

License

MIT

Source: README.md at commit 8a6e2ff

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts