DEPENDENCY EVIDENCE

Know what changed before you depend on it.

For teams using external agents and MCP servers: inspect evidence, watch changes, record what you accepted.

Check a client configuration locally · Agency pilot

io.github.bbcbasic/testgraph

Runtime observation: 2026-11-07T21:58:15.810833+00:00 · State: live

Watches availability, tools and schemas, auth access, endpoints and lifecycle notices. Only complete schemas are compared. OAuth scope and consent-screen changes are not measured.

Agent and MCP watches share your plan's budget. Manage watches.

Current recorded evidence

{
  "auth": "anonymous",
  "availability": "live",
  "endpoint": "https://testgraph.21dle.co.uk/mcp-v2",
  "legal_identity": null,
  "lifecycle": null,
  "observed_at": "2026-11-07T21:58:15.810833+00:00",
  "registry_status": null,
  "subject": {
    "id": "io.github.bbcbasic/testgraph",
    "kind": "mcp"
  },
  "tools": {
    "names": [
      "affirm_subject_classification",
      "assert_location",
      "claim_deliberation",
      "correct_subject_fact",
      "create_deliberation",
      "delete_experience",
      "enrich_subject",
      "fetch",
      "get_deliberation",
      "get_induction",
      "get_location_assertions",
      "get_server_info",
      "get_subject_classification",
      "get_subject_type_path",
      "list_child_subject_types",
      "list_my_mcp_interactions",
      "list_my_workflows",
      "list_open_deliberations",
      "list_reviews_by_visibility",
      "list_root_subject_types",
      "propose_subject_reclassification",
      "record_resolution",
      "register_field",
      "register_subject_type_alias",
      "reopen_subject_classification",
      "resolve_location_assertion",
      "resolve_subject",
      "resolve_subject_hierarchy",
      "resolve_subject_type",
      "retire_type_relationship",
      "save_assessment",
      "save_experience",
      "search",
      "set_review_visibility",
      "set_type_relationship",
      "submit_contribution",
      "vocabulary_index"
    ],
    "names_truncated": false,
    "sha256": "3d4f930588ed3a8299a30332bf003d82620574499e5cd9b7f3b8feebf0f590b3"
  },
  "tools_complete": true,
  "tools_observed_at": "2026-11-07T21:58:15.810833+00:00",
  "version": null
}

Pin and review

Keep an accepted snapshot in agents.lock.json. CI returns allow, review or block with reasons.

Gaps default to review. A lock records your acceptance, not a supplier attestation.

API reference

Test an explicit task

Verified domain owners can publish up to five exact-match sandbox fixtures and opt in to a test run. Results include latency, output hashes and regressions.

POST /api/v1/dependencies/task-checks?domain=… while signed in. See the integration guide.

Inspect proof coverage

Domain control, a declared business identifier and a name-matched company record are separate evidence.

Current coverage and measurement date · Verify your domain

Optional SealKeeper evidence

Verify issuer signatures, subject and freshness from the public key document. Task evidence stays separate from Agenstry measurements.

A valid SEAL does not establish domain ownership, legal identity, key possession or execution permission.

Credential verification API · Issuer documentation

Smithery endpoint migration · Agent monitoring · Methodology