DEPENDENCY EVIDENCE

Know what changed before you depend on it.

For teams using external agents and MCP servers: inspect measured evidence, watch changes, and keep a record of what your team accepted. Unknown evidence stays explicit.

Have a client configuration? Extract and check its public endpoints locally. Maintaining integrations for clients? Explore the agency pilot.

io.github.zvmzaretsky/utility-belt

Runtime observation: 2026-10-22T21:39:53.145061+00:00 · State: live

Watch availability, tools and parameter schemas, authentication access, endpoint changes and lifecycle notices. Only complete observed schemas are compared. OAuth scope and consent-screen changes are not currently measured.

Sign-in required. Agent and MCP watches share the existing Free / Pro / Enterprise budget. Manage watches.

Current recorded evidence

{
  "auth": "anonymous",
  "availability": "live",
  "endpoint": "https://belt.fabtally.com/mcp",
  "legal_identity": null,
  "lifecycle": null,
  "observed_at": "2026-10-22T21:39:53.145061+00:00",
  "registry_status": null,
  "subject": {
    "id": "io.github.zvmzaretsky/utility-belt",
    "kind": "mcp"
  },
  "tools": {
    "names": [
      "convert",
      "cron",
      "currency",
      "datemath",
      "diff",
      "encode",
      "hash",
      "id",
      "jsonschema",
      "regex",
      "rrule",
      "text",
      "timezone"
    ],
    "names_truncated": false,
    "sha256": "f27475d8f0c330b39ad92f1754ea922f1e8e2ada112056ce4f4ffd8ad9166f38"
  },
  "tools_complete": true,
  "tools_observed_at": "2026-10-22T21:39:53.145061+00:00",
  "version": null
}

Pin and review

Keep an accepted snapshot in agents.lock.json. CI compares it with current evidence and returns allow, review or block with reasons, before/after data and policy hashes.

Default gaps require review. Configure stricter handling explicitly. A lock records your acceptance; it is 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 fixture version, latency, output hashes and comparable regressions. Cost remains unknown when unobserved.

Run with POST /api/v1/dependencies/task-checks?domain=… while signed in. Read the schema and example in the integration guide.

Inspect proof coverage

Domain control, a declared business identifier and an active name-matched company record are separate evidence. Zero verified records means zero recorded proof.

Current coverage and measurement date · Verify your domain

Optional SealKeeper evidence

Verify issuer signatures, subject and credential freshness using the public key document. Keep its task evidence categories 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