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

in.railroute/journey-planner

Runtime observation: 2026-11-06T12:16:33.565329+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://www.railroute.in/api/mcp",
  "legal_identity": null,
  "lifecycle": null,
  "observed_at": "2026-11-06T12:16:33.565329+00:00",
  "registry_status": null,
  "subject": {
    "id": "in.railroute/journey-planner",
    "kind": "mcp"
  },
  "tools": {
    "names": [
      "check_train_options",
      "find_place",
      "journey_calendar",
      "nearby_stations",
      "next_confirmed_date",
      "plan_journey",
      "station_departures",
      "train_schedule"
    ],
    "names_truncated": false,
    "sha256": "719222d47961f2c18f83d5574528dbde216103633ffc8a7bf52512a1051c2c3e"
  },
  "tools_complete": true,
  "tools_observed_at": "2026-11-06T12:16:33.565329+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