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.
Runtime observation: 2026-10-23T21:56:21.664124+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 to watch this MCP serverSign-in required. Agent and MCP watches share the existing Free / Pro / Enterprise budget. Manage watches.
{
"auth": "anonymous",
"availability": "live",
"endpoint": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/accept-ok/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-23T21:56:21.664124+00:00",
"registry_status": null,
"subject": {
"id": "io.github.sadri-dridi/accept-ok",
"kind": "mcp"
},
"tools": {
"names": [
"accept-ok",
"agent-ads-index",
"agent-tool-index",
"browser-url-ok",
"calc-eval",
"citation",
"compatibility",
"domain-shape",
"fetch-status",
"figma-url-shape",
"file-path-ok",
"geo-hint",
"github-repo-shape",
"hn-front-count",
"iana-zones",
"inspect-robots",
"jira-key-shape",
"lib-docs-hint",
"memory-key-count",
"normalize-url",
"people-search-index",
"playwright-url-ok",
"search-query-len",
"status-catalog",
"think-steps",
"timezone",
"utc-time",
"validate-json",
"weather-hint",
"web-fetch",
"wiki-title-ok"
],
"names_truncated": false,
"sha256": "f064596330d97586ef4e4400510e3e962c14823c39ec9a8d66a3ffa56f8c4126"
},
"tools_complete": true,
"tools_observed_at": "2026-10-23T21:56:21.664124+00:00",
"version": null
}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 referenceVerified 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.
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 domainVerify 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 documentationSmithery endpoint migration · Agent monitoring · Methodology