Skip to content
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

online.agentmart/procurement

Runtime observation: 2026-11-08T22:17:26.009666+00:00 · State: auth_required

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.

Sign in to watch this MCP server

Agent and MCP watches share your plan's budget. Manage watches.

Current recorded evidence
{
  "auth": "required",
  "availability": "auth_required",
  "endpoint": "https://mcp.agentmart.online/mcp",
  "legal_identity": null,
  "lifecycle": null,
  "observed_at": "2026-11-08T22:17:26.009666+00:00",
  "registry_status": null,
  "subject": {
    "id": "online.agentmart/procurement",
    "kind": "mcp"
  },
  "tools": {
    "names": [
      "billing_status",
      "calibrate",
      "create_billing_portal",
      "create_checkout",
      "execute",
      "procure",
      "quote",
      "recommend",
      "usage"
    ],
    "names_truncated": false,
    "sha256": "b97994ec59d26b73a3d09e8a0a6007611b5a73905826edf59a0ee0e96c756da0"
  },
  "tools_complete": true,
  "tools_observed_at": "2026-11-01T22:14:40.174874+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.

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