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.entia-systems-core/entity-verification

Runtime observation: 2026-11-01T09:51:29.266606+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://mcp.entia.systems/mcp",
  "legal_identity": null,
  "lifecycle": null,
  "observed_at": "2026-11-01T09:51:29.266606+00:00",
  "registry_status": null,
  "subject": {
    "id": "io.github.entia-systems-core/entity-verification",
    "kind": "mcp"
  },
  "tools": {
    "names": [
      "entity_lookup",
      "fetch",
      "get_competitors",
      "get_entia_home",
      "get_entity_home_projection",
      "get_full_dossier",
      "get_identity_verification",
      "get_platform_stats",
      "get_showcase",
      "professional_lookup",
      "run_risk_audit",
      "search",
      "search_entities",
      "verify_vat",
      "zone_profile"
    ],
    "names_truncated": false,
    "sha256": "e84c309fc10655f8b276b0c4a23b9253beefe4116f38c4089c5fade5ee81ba57"
  },
  "tools_complete": true,
  "tools_observed_at": "2026-11-01T09:51:29.266606+00:00",
  "version": "3.6.0"
}

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