Forge AI Accountability

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.github.forgeorbital/forge-ai-accountability and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 2 Nov 2026. Not supplied by the maker.

• list_scenarios

  Lists the five sample scenarios for the fictional Acme Mutual Insurance that run_check accepts, with their evidence ids. Demo data only.

• 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.

• 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

• 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. Repla

• 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

• 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.

• review_agent_workflow

  Run the Forge evaluator and optimizer on synthetic examples or supplied labeled baseline/candidate outputs and token usage. Use payload={sample_mode: improved}, regression, or changed_path for example