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-22T22:10:04.364239+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://1cent.maxzoa.ru/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T22:10:04.364239+00:00",
"registry_status": null,
"subject": {
"id": "ru.maxzoa/1cent",
"kind": "mcp"
},
"tools": {
"names": [
"catalog.tools.search",
"demo.live.pulse",
"demo.url.pulse",
"web.batch.url_status",
"web.site.coherence",
"web.site.feeds",
"web.site.llms_txt",
"web.site.openapi",
"web.site.robots",
"web.site.security_txt",
"web.site.sitemaps",
"web.url.access_flags",
"web.url.accessibility",
"web.url.canonical",
"web.url.changed",
"web.url.citations",
"web.url.content_quality",
"web.url.content_type",
"web.url.diff",
"web.url.extract",
"web.url.hash",
"web.url.headers",
"web.url.headings",
"web.url.images",
"web.url.jsonld",
"web.url.language",
"web.url.links",
"web.url.localization",
"web.url.markdown",
"web.url.metadata",
"web.url.passport",
"web.url.performance",
"web.url.policy",
"web.url.pulse",
"web.url.rag_chunks",
"web.url.redirects",
"web.url.schema_validation",
"web.url.security_headers",
"web.url.social_cards",
"web.url.status",
"web.url.tables",
"web.url.technology",
"web.url.text",
"web.url.timing",
"web.url.tls",
"web.url.word_stats"
],
"names_truncated": false,
"sha256": "6a2e48d49aaa5c128e64d8676d335f7154e54ef5eb32556019bcdb78dcc3d5b2"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T22:10:04.364239+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