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-30T11:39:04.571707+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://mcp.uptimepage.dev/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-30T11:39:04.571707+00:00",
"registry_status": null,
"subject": {
"id": "dev.uptimepage/uptimepage",
"kind": "mcp"
},
"tools": {
"names": [
"acknowledge_incident",
"add_status_page_components",
"cancel_maintenance",
"create_maintenance",
"create_monitor",
"create_monitors",
"create_status_page",
"get_flow_runs",
"get_flow_step_trend",
"get_incident",
"get_incident_metrics",
"get_maintenance",
"get_monitor",
"get_monitor_history",
"get_org_health",
"get_org_usage",
"get_status_page",
"list_incidents",
"list_maintenance",
"list_monitor_groups",
"list_monitors",
"list_notification_channels",
"list_regions",
"list_status_page_viewers",
"list_status_pages",
"list_tags",
"list_variables",
"pause_monitor",
"post_incident_update",
"post_maintenance_update",
"publish_incident",
"resolve_incident",
"resume_monitor",
"run_check_now",
"set_monitor_state",
"unpublish_incident",
"update_maintenance",
"update_monitor",
"update_monitor_group",
"update_status_page",
"update_status_page_component"
],
"names_truncated": false,
"sha256": "58105acb20b2950180a9665f93e3fe53ffd1c9f47030d05cc1ef679a01fab4f9"
},
"tools_complete": true,
"tools_observed_at": "2026-10-30T11:39:04.571707+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