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

com.nittim/nittim

Runtime observation: 2026-11-13T00:17:00.647917+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://nittim.com/api/mcp",
  "legal_identity": null,
  "lifecycle": null,
  "observed_at": "2026-11-13T00:17:00.647917+00:00",
  "registry_status": null,
  "subject": {
    "id": "com.nittim/nittim",
    "kind": "mcp"
  },
  "tools": {
    "names": [
      "audit_repo",
      "audit_source",
      "describe_protocol",
      "dispute_finding",
      "estimate_audit",
      "get_audit",
      "get_loop",
      "judge_output",
      "list_modules",
      "mint_key",
      "preview_upload",
      "report_loop",
      "run_module",
      "scan_source",
      "verify_fix"
    ],
    "names_truncated": false,
    "sha256": "fb9102ef1ab02fbbf32f5e8a61f57fe79cc745070a930fb1a236311248ff9f61"
  },
  "tools_complete": true,
  "tools_observed_at": "2026-11-13T00:17:00.647917+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