Security
Integrity of the record, posture of the connectors that carry actions out, and an on-demand check of an MCP server’s advertised tools. Ordered by consequence.
Audit chain
Chain intact 47 record(s) verified
sha256:2735a53f8c20d0c24bf6a0d5f1dafb7b713b01f4dea0fac0c76ce67db9c6882c
Full verification and the records themselves →
Connector posture
| Connector | Health | Detail (as reported) |
|---|---|---|
| simulation | healthy | 3 simulated tool(s) |
An MCP connector reports drift when its advertised tool surface no longer matches the pinned manifest. The added, removed and modified tools are listed by arc mcp diff; the API exposes only this message.
MCP manifest scan
Results are not saved, and scanning registers nothing. The API computes a report and returns it; there is no findings store, so a reload scans again and leaves no trace. Run arc mcp scan in CI for a durable record.
Inert in this capture — a scan needs the live API. See a real scan of a poisoned manifest, produced by this build.
Findings appear here after a scan. A reload scans again and changes nothing.