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

io.github.jmxisnext/academic-evidence-pack

Runtime observation: 2026-11-06T20:32:24.386845+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.

Sign in to watch this MCP server

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

Current recorded evidence
{
  "auth": "anonymous",
  "availability": "live",
  "endpoint": "https://aep-api.fly.dev/mcp",
  "legal_identity": null,
  "lifecycle": null,
  "observed_at": "2026-11-06T20:32:24.386845+00:00",
  "registry_status": null,
  "subject": {
    "id": "io.github.jmxisnext/academic-evidence-pack",
    "kind": "mcp"
  },
  "tools": {
    "names": [
      "citation_report",
      "citation_report_large",
      "citation_report_preview",
      "citation_report_receipt",
      "evidence_pack",
      "evidence_pack_preview"
    ],
    "names_truncated": false,
    "sha256": "c32e0f212c1e46c5c96a1d95cfebf2d8ba95174331dc6a49a32c29030ad2141d"
  },
  "tools_complete": true,
  "tools_observed_at": "2026-11-06T20:32:24.386845+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