Forge AI Accountability
REMOTE · DEMO.FORGEORBITAL.COM
Demo of Forge decision accountability on fictional Acme Mutual: signed, replayable records.
Available components
Last scanned (2 hours ago)
Scores higher than 52% of remote servers
Unreachable for 2 days in a row. Last reached 3 Nov 2026.
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security14
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Schema quality: 0 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 3 Nov 26 +1
- Tool “review_agent_workflow” rewrote its description, which is the text the model reads security
- Schema quality: 71 → 90 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 65
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 5 Nov 2026 · Probed https://demo.forgeorbital.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of demo.forgeorbital.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| forgeorbital.com. | present | 2371 | 13 | Verified |
| demo.forgeorbital.com. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://demo.forgeorbital.com/mcp | Unreachable | ||
| http (plaintext) | http://demo.forgeorbital.com/mcp | HTTPS enforced |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
explain_verdict Explain a Forge Orbital verdict in plain English ~56
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.
| Name | Type | Req | Description |
|---|---|---|---|
| record | object | yes | – |
No output schema declared.
No examples provided.
get_attestation_summary Summarize what a Forge Orbital record attests ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| record | object | yes | – |
No output schema declared.
No examples provided.
list_scenarios List demo scenarios ~36
Lists the five sample scenarios for the fictional Acme Mutual Insurance that run_check accepts, with their evidence ids. Demo data only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
replay_decision_record Replay a Forge Orbital decision from its inputs ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| record | object | yes | – |
| scenario_id | string | yes | – |
| withdraw_evidence | – | – | – |
No output schema declared.
No examples provided.
review_agent_workflow Evaluate an agent change and explore cost options ~274
Run the Forge accountability engine evaluator and optimizer on synthetic examples or supplied labeled old/new outputs. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| payload | object | yes | – |
No output schema declared.
No examples provided.
run_check Run a Forge Orbital check on a sample scenario ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| scenario_id | string | yes | – |
| withdraw_evidence | – | – | – |
No output schema declared.
No examples provided.
verify_decision_record Verify a Forge Orbital decision record ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| record | – | – | – |
| record_id | – | – | – |
No output schema declared.
No examples provided.
How do I install the Forge AI Accountability MCP server?
Forge AI Accountability is a hosted endpoint at https://demo.forgeorbital.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · demo.forgeorbital.com
claude mcp add --transport http forgeorbital-forge-ai-accountability 'https://demo.forgeorbital.com/mcp'
What is the Forge AI Accountability MCP server?
Forge AI Accountability is an MCP server listed in the public MCP registry as io.github.forgeorbital/forge-ai-accountability. Demo of Forge decision accountability on fictional Acme Mutual: signed, replayable records. This page covers its hosted endpoint (https://demo.forgeorbital.com/mcp).
Is the Forge AI Accountability MCP server safe to use?
Forge AI Accountability scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Forge AI Accountability MCP server expose?
Forge AI Accountability exposes 7 tools: list_scenarios, run_check, verify_decision_record, replay_decision_record, get_attestation_summary, and 2 more. Their descriptions and schemas cost roughly 716 tokens of context every time the server is loaded.
Does the Forge AI Accountability MCP server require authentication?
Its publisher declares no required credentials for Forge AI Accountability. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Forge AI Accountability MCP server still maintained?
Forge AI Accountability is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.