mcpbeat Sign in

Forge AI Accountability MCP Server

answering

Forge AI Accountability is answering right now. Last checked 9 min ago. It exposes 7 tools.

Demo of Forge decision accountability on fictional Acme Mutual: signed, replayable records.

Uptime history 6 days of history
6 days agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
369 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 3 November 2026. No other catalogue keeps this.

4 Nov a tool description was rewritten review_agent_workflow
3 Nov a tool description was rewritten review_agent_workflow

Nothing serious here today

Today is the operative word: we check Forge AI Accountability every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add forge-ai-accountability --transport http https://demo.forgeorbital.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://demo.forgeorbital.com/mcp
~/.codex/config.toml
[mcp_servers.forge-ai-accountability]
url = "https://demo.forgeorbital.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "forge-ai-accountability": {
      "url": "https://demo.forgeorbital.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "forge-ai-accountability": {
      "type": "http",
      "url": "https://demo.forgeorbital.com/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

attestation
get_attestation_summary
Verifies a Forge Orbital demo decision record against the pinned demo key and summarizes what it attests: signature status, the decision, whether the engine abstained, whether human review is required, and how many evidence items were used. Does not store the record. Demo records only.
explain
explain_verdict
Explains, in plain English, why Forge Orbital reached the verdict in a demo decision record and what evidence a reviewer would need to change it. Read-only, stateless, demo data only.
replay
replay_decision_record
Replays a Forge Orbital demo decision: re-runs the deterministic engine on the same sample scenario (and any withdrawn evidence) and checks that the replay key and the decision match the record. Replayability is the point: the same inputs and engine version give the same decision. Reads nothing about the user. Demo only, fictional sample data.
review
review_agent_workflow
Use Evaluate and Optimise to compare synthetic examples or supplied labeled old/new outputs with the Forge accountability engine. For samples use payload={"sample_mode":"improved"}, or regression/changed_path. For a user-supplied comparison, translate only their supplied actions into this exact format: payload={"workflow":"User test","cases":[{"id":"case-1","expected":{"action":"hold"},"baseline":{"output":{"action":"allow"},"trajectory":[]},"candidate":{"output":{"action":"hold"},"trajectory":[]}}]}. Replace example actions with the user actions; never invent labels or steps. If the user has not said what should happen, ask them in plain English before scoring. The user never needs to write JSON or know these field names. Cases need id, expected.action, baseline.output.action, baseline.trajectory, candidate.output.action and candidate.trajectory. Use empty trajectory arrays when no action steps were supplied. Do not use plain strings for expected/baseline/candidate. Omit usage entirely unless token usage was supplied. If a format error occurs, repair the structure without changing the evidence and retry. A description alone returns a standard preparation checklist, not a measured evaluation. No code runs, external agent calls, changes or deployment. Synthetic prices are unsigned estimates, never approved savings.
run
run_check
Computes a Forge Orbital verdict for one of five fictional Acme Mutual Insurance scenarios and returns it with a signed decision record in the response. Read-only: nothing is stored, sent or changed. Optionally withdraw evidence ids to see how the verdict changes. Demo only: sample rules and sample evidence, not connected to the user's systems, policies or live actions.
scenarios
list_scenarios
Lists the five sample scenarios for the fictional Acme Mutual Insurance that run_check accepts, with their evidence ids. Demo data only.
verify
verify_decision_record
Verifies the Ed25519 signature of a Forge Orbital demo decision record against the published demo key id. Pass the full signed record object returned by run_check (this demo keeps nothing, so a record id alone cannot be looked up). Editing any field makes verification fail. Demo records only.

Endpoints

URLTransportStateLatencyChecked
https://demo.forgeorbital.com/mcp streamable-http answering 373 ms 9 min ago

Alternatives to Forge AI Accountability

same job, measured the same way
Decision Anchor
by decision-anchor

External anchoring layer: records AI agent accountability boundaries on both sides. Content-blind.

30 tools answering
Aga MCP Server
by attestedintelligence

Verifiable decision records for AI agents: signed receipts for calls to its own governed tools.

60 installs/wk local only
mnema: decision records for AI coding agents
by mnema-work

Signed, append-only decision records for AI coding agents, over MCP. Verify them offline.

331 installs/wk local only
Agentic Wallet Guardian V3
by rudimentall1

Explainable ALLOW/WARN/BLOCK risk decisions for AI agent actions before execution, signed as OAA.

203 installs/wk local only
Tersign Evidence
by tersignhq

The record layer for the machine age: counter-signed receipts and agent action records.

106 installs/wk local only
Umbra Proof
by beepboop2025

Verify Umbra bridge accountability proofs (signed receipts, checkpoints, Merkle inclusion).

local only
PEAC Protocol: Signed interaction receipts
by peacprotocol

Portable signed records for agent, API, MCP, and cross-runtime interactions.

113 installs/wk local only
BountyRadar MCP
by panstories

Ranked feed of AI-agent-solvable bounties, scored for solvability and competition.

answering

Forge AI Accountability — questions

Answers built from our own checks of this server.

What can Forge AI Accountability do?
It exposes 7 tools, read directly from the server on our last check. Among them: explain_verdict, get_attestation_summary, list_scenarios, replay_decision_record, review_agent_workflow, run_check and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Forge AI Accountability working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 369 ms. The bar chart above shows every period we have measured.
How do I connect Forge AI Accountability?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Forge AI Accountability need an API key?
No. Forge AI Accountability completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Forge AI Accountability?
It answers our handshake in 369 ms on average, which is faster than 35% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.