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.pipeworx-io/19hz

Runtime observation: 2026-11-11T02:53:42.644009+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://gateway.pipeworx.io/19hz/mcp",
  "legal_identity": null,
  "lifecycle": null,
  "observed_at": "2026-11-11T02:53:42.644009+00:00",
  "registry_status": null,
  "subject": {
    "id": "io.github.pipeworx-io/19hz",
    "kind": "mcp"
  },
  "tools": {
    "names": [
      "ai_visibility_check",
      "archive_compare",
      "archive_evidence",
      "ask_pipeworx",
      "ask_pipeworx_beta",
      "ask_pipeworx_grounded",
      "bet_research",
      "classify_row",
      "company_facts",
      "company_register_search",
      "compare_entities",
      "deep_research",
      "discover_tools",
      "entity_profile",
      "events",
      "forget",
      "generate_llms_txt",
      "kalshi_weather_edge",
      "list_subscriptions",
      "pipeworx_feedback",
      "pipeworx_trending",
      "polymarket_arbitrage",
      "polymarket_edge_tracker",
      "polymarket_edges",
      "polymarket_fill_risk",
      "polymarket_kalshi_spread",
      "prediction_calibration",
      "recall",
      "recent_alerts",
      "recent_changes",
      "regions",
      "release_calendar_markets",
      "remember",
      "research_row",
      "resolution_audit",
      "resolution_diff",
      "resolve_entity",
      "scan_competitor_ai_presence",
      "scan_dependency",
      "search_within",
      "subscribe",
      "suggest_questions",
      "unsubscribe",
      "updown_divergence_rate",
      "updown_venue_compare",
      "validate_claim"
    ],
    "names_truncated": false,
    "sha256": "fd01971000371530395cc957e3ba8979b098d7dbbe7b5b7298ff5d1341c3a209"
  },
  "tools_complete": true,
  "tools_observed_at": "2026-11-11T02:53:42.644009+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