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.supero-platform/supero

Runtime observation: 2026-11-07T10:31:11.374351+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://api.supero.dev/mcp/v1/messages",
  "legal_identity": null,
  "lifecycle": null,
  "observed_at": "2026-11-07T10:31:11.374351+00:00",
  "registry_status": null,
  "subject": {
    "id": "io.github.supero-platform/supero",
    "kind": "mcp"
  },
  "tools": {
    "names": [
      "apikey_get_scope",
      "build_audit",
      "build_bind_data_source",
      "build_configure_services",
      "build_connect_data_source",
      "build_create_project",
      "build_deploy",
      "build_deploy_status",
      "build_discover_source",
      "build_doctor",
      "build_e2e_test",
      "build_e2e_test_status",
      "build_get_bundle",
      "build_get_examples",
      "build_get_project",
      "build_get_service_contract",
      "build_get_skills",
      "build_go_live",
      "build_import_services",
      "build_list_bound_schemas",
      "build_list_capabilities",
      "build_list_data_sources",
      "build_list_projects",
      "build_logs",
      "build_plan",
      "build_publish",
      "build_recommend_integrations",
      "build_replace_project",
      "build_run_data_source",
      "build_set_project_mode",
      "build_smoke_test",
      "build_stage_bundle",
      "build_teardown",
      "build_update_project",
      "build_validate",
      "build_verify",
      "build_whoami",
      "connector_cancel",
      "connector_disable",
      "connector_discover",
      "connector_discover_results",
      "connector_discover_status",
      "connector_enable",
      "connector_plugins",
      "connector_run",
      "connector_status",
      "connector_test",
      "connector_test_config",
      "crud_create",
      "crud_delete",
      "crud_get",
      "crud_search",
      "crud_update",
      "project_link_schemas",
      "rbac_check_permission",
      "rbac_get_my_access",
      "schema_delete",
      "schema_get",
      "schema_list",
      "schema_list_project",
      "schema_save",
      "schema_update",
      "schema_validate",
      "sdk_download",
      "sdk_generate",
      "sdk_list",
      "sdk_status"
    ],
    "names_truncated": false,
    "sha256": "88191c7d13e4c1dd25e82f2de368d16193c1a999eb395268680fffcc2ad1d265"
  },
  "tools_complete": true,
  "tools_observed_at": "2026-11-07T10:31:11.374351+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