Skip to main content
Glama
VeritasActa

acta-mcp

by VeritasActa

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ACTA_DEVICE_IDNoDevice identity for budget/rate limiting (auto-generated if not set)
ACTA_INSTANCE_URLNoThe Acta instance to connect tohttps://veritasacta.com

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
acta_contributeA

Submit a typed contribution to the Acta public record. Questions have no evidence burden. Factual claims require a source or reasoning. Opinion/hypothesis claims require uncertainty. Predictions require resolution criteria, date, source, and rule.

acta_respondA

Submit a response to an existing entry. Evidence requires source + stance. Challenges require target_assertion + basis + argument (min 20 chars). Updates require update_type. Resolutions require outcome + source + resolution_type.

acta_queryA

Browse the Acta public record. List topics (optionally filtered), get entries for a topic (with type/state filters), or look up a single entry with its responses.

acta_discoverA

Find actionable work across the Acta record. Surfaces contested records needing evidence, claims with no evidence, predictions approaching resolution, and recently active topics. This is the "where am I needed?" tool.

acta_verifyA

Verify the hash chain integrity for a specific topic. Returns chain length, chain head hash, and any integrity issues. Note: this is operator-served verification. For independent verification, use acta_export and run verify.js locally.

acta_exportA

Export the full hash chain for a topic. Returns all entries with hashes for independent verification using tools/verify.js. Use this when you need to audit the record independently.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: contributing, discovering, exporting, querying, responding, and verifying. No two tools overlap in functionality.

Naming Consistency5/5

All tools follow a consistent 'acta_<verb>' pattern using snake_case, making the naming predictable and easy to understand.

Tool Count5/5

With 6 tools covering submission, browsing, responding, discovery, export, and verification, the tool count is well-scoped for the domain of a public record system.

Completeness5/5

The tool set covers all essential operations for an append-only record system: contributing, querying, responding, discovering actionable items, and verifying integrity via export and local verification.

Maintenance

ActivityInactive
ResponsivenessNo issues