io.github.tomjwxf/acta-mcp
NPM · ACTA-MCP · SCANNED AUG 3
Contribute, challenge, verify, and query contestable public records on Veritas Acta.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 124 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 842 tokens (~140/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · acta-mcp
claude mcp add tomjwxf-acta-mcp -- npx -y acta-mcp
codex mcp add tomjwxf-acta-mcp -- npx -y acta-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tomjwxf-acta-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"acta-mcp"
],
"enabled": true
}
}
} openclaw mcp add tomjwxf-acta-mcp --command npx --arg -y --arg acta-mcp
mcp_servers:
tomjwxf-acta-mcp:
command: "npx"
args: ["-y", "acta-mcp"] {
"mcpServers": {
"tomjwxf-acta-mcp": {
"command": "npx",
"args": [
"-y",
"acta-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +47
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: MIT functional
- 31 Jul 26 −25
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +21
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: unverified functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- First check of Schema quality: fail functional
- 27 Jul 26 24
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 96 packages
96 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
acta_contribute ~241
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Full text of the contribution |
| category | string | — | Required for claims |
| provenance | object | — | Optional AI authorship metadata |
| reasoning | string | — | Reasoning (alternative to source for factual claims) |
| resolution_criteria | string | — | How to determine if confirmed/refuted (required for predictions) |
| resolution_date | string | — | ISO-8601 future date (required for predictions) |
| resolution_rule | string | — | Who/what triggers resolution (required for predictions) |
| resolution_source | string | — | Authoritative source for resolution (required for predictions) |
| source | string | — | URL to supporting evidence (required for factual claims) |
| topic | string | yes | Topic slug (e.g. "ai-regulation-2026") |
| type | string | yes | Contribution type |
| uncertainty | string | — | Uncertainty statement (required for opinion/hypothesis claims) |
No output schema declared.
No examples provided.
acta_discover ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Maximum results (default: 10) |
| mode | string | yes | contested: records in contested state. needs_evidence: claims/predictions with no linked evidence. approaching_resolution: predictions with resolution dates within 30 days. recent_activity: topics wi… |
No output schema declared.
No examples provided.
acta_export ~54
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.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | Topic slug to export |
No output schema declared.
No examples provided.
acta_query ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | list_topics: browse topics. feed: entries for a topic. entry: single entry with responses. |
| entry_id | string | — | Entry ID (required for entry action) |
| q | string | — | Filter topic names by substring (for list_topics) |
| state | string | — | Filter feed by computed state |
| topic | string | — | Topic slug (required for feed action) |
| type | string | — | Filter feed by contribution type |
No output schema declared.
No examples provided.
acta_respond ~231
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.
| Name | Type | Req | Description |
|---|---|---|---|
| argument | string | — | Substantive refutation (min 20 chars, required for challenges) |
| basis | string | — | Required for challenges |
| body | string | yes | Response text |
| outcome | string | — | Resolution outcome (required for resolutions) |
| provenance | object | — | Optional AI authorship metadata |
| resolution_type | string | — | Required for resolutions |
| source | string | — | Source URL (required for evidence, counter_evidence/source_unreliable challenges, and resolutions) |
| stance | string | — | Required for evidence |
| target_assertion | string | — | Quote the specific assertion being challenged (min 5 chars, required for challenges) |
| target_id | string | yes | Entry ID being responded to |
| topic | string | yes | Topic slug |
| type | string | yes | Response type |
| update_type | string | — | Required for updates |
No output schema declared.
No examples provided.
acta_verify ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | Topic slug to verify |
No output schema declared.
No examples provided.