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-28T13:19:57.453681+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://448c.org/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-28T13:19:57.453681+00:00",
"registry_status": null,
"subject": {
"id": "org.448c/sentinel",
"kind": "mcp"
},
"tools": {
"names": [
"attest_create",
"attest_read",
"check_address",
"check_url",
"claim_acquire",
"claim_acquire_free",
"claim_read",
"claim_release",
"claim_renew",
"create_inbox",
"deadman_confirm",
"deadman_read",
"deadman_register",
"dns_lookup",
"dns_release",
"dns_renew",
"dns_rent",
"dns_rent_free",
"dns_set_records",
"drift_baseline",
"drift_check",
"drift_venues",
"execute",
"free_inbox",
"handoff_deposit",
"handoff_read",
"inbox_status",
"listing_promote",
"pay_receipt",
"pay_requirements",
"pay_send",
"placement_cancel",
"placement_order",
"placement_ready",
"placement_status",
"placement_venues",
"read_inbox",
"release_inbox",
"search_listings",
"service_card",
"storage_buy",
"storage_delete",
"storage_list",
"storage_read",
"storage_renew",
"storage_replace",
"storage_usage",
"watch_read",
"watch_register",
"x402_supported",
"x402_verify"
],
"names_truncated": false,
"sha256": "0d69ae36aa192f0b9401ba103792dfc5d5de59e49a83a86acecc5bccaf99061c"
},
"tools_complete": true,
"tools_observed_at": "2026-10-28T13:19:57.453681+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