Acting as operations@arctransformationgroup.com (configured, not authenticated)

API http://127.0.0.1:8787 ok v2.1.0

← Assurance

Covering 2026-09-26 09:18:30Z to 2026-10-26 09:18:30Z — 7 action(s) and 8 evidence record(s) fell in that window. Every status below describes that period and nothing outside it.

Control
ARC-AI-007 (version 1)
Assurance
automated
Evaluated
2026-10-26 09:18:30Z
Run
arc_run_6fddf9…
Integrity digest
sha256:78c62c6a3fa6399673802b8955fcb0b4d0df67e3e324dd9a904dd3670ed43a7c

What this result does not establish

  • A pinned digest makes drift detectable. It does not detect drift on its own — that needs a scan, which ARC performs on demand rather than on a schedule in this release.
  • The scan reads what the server declares about itself. A server that lies about its own tool descriptions is not caught by reading them.

Observations

0 examined, 0 failing

This assessment examined nothing. Its summary says why.

{
  "id": "arc_asm_df8365c9e2d578dc6c7f7c83cc8695af",
  "schemaVersion": 2,
  "runId": "arc_run_6fddf961fa6f723fc7c7aff98056028d",
  "controlId": "ARC-AI-007",
  "controlVersion": 1,
  "organizationId": "default",
  "status": "not_applicable",
  "assurance": "automated",
  "summary": "No tool is executed by an MCP connector.",
  "observations": [],
  "window": {
    "from": "2026-09-26T09:18:30.472Z",
    "to": "2026-10-26T09:18:30.472Z",
    "actionsConsidered": 7,
    "evidenceConsidered": 8
  },
  "limitations": [
    "A pinned digest makes drift detectable. It does not detect drift on its own — that needs a scan, which ARC performs on demand rather than on a schedule in this release.",
    "The scan reads what the server declares about itself. A server that lies about its own tool descriptions is not caught by reading them."
  ],
  "findingIds": [],
  "evaluatedAt": "2026-10-26T09:18:30.472Z",
  "evaluationMs": 0.092085,
  "integrityDigest": "sha256:78c62c6a3fa6399673802b8955fcb0b4d0df67e3e324dd9a904dd3670ed43a7c"
}