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-22T13:51:04.872667+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://api.hyperping.io/v1/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T13:51:04.872667+00:00",
"registry_status": null,
"subject": {
"id": "com.hyperping/hyperping",
"kind": "mcp"
},
"tools": {
"names": [
"acknowledge_outage",
"add_status_page_incident_update",
"add_status_page_services",
"cancel_maintenance_window",
"complete_maintenance_window",
"create_log_dashboard_from_template",
"create_maintenance_window",
"create_monitor",
"create_outage",
"create_status_page",
"create_status_page_incident",
"edit_status_page_incident_update",
"escalate_outage",
"find_correlated_outages",
"get_browser_run",
"get_escalation_policy",
"get_healthcheck",
"get_integration",
"get_maintenance_window",
"get_monitor",
"get_monitor_anomalies",
"get_monitor_http_logs",
"get_monitor_mtta",
"get_monitor_mttr",
"get_monitor_outages",
"get_monitor_response_time",
"get_monitor_uptime",
"get_on_call_now",
"get_on_call_schedule",
"get_outage",
"get_outage_alerts",
"get_outage_checks",
"get_outage_logs",
"get_outage_timeline",
"get_project_report",
"get_recent_changes",
"get_server",
"get_status_page",
"get_status_page_incident",
"get_status_summary",
"list_audit_log",
"list_browser_runs",
"list_escalation_policies",
"list_healthchecks",
"list_integrations",
"list_log_dashboards",
"list_maintenance_windows",
"list_monitors",
"list_on_call_schedules",
"list_outages",
"list_recent_alerts",
"list_servers",
"list_status_page_incidents",
"list_status_pages",
"list_team_members",
"pause_monitor",
"remove_status_page_services",
"resolve_outage",
"resolve_status_page_incident",
"resume_monitor",
"run_check_now",
"run_log_chart",
"search_logs",
"search_monitors_by_name",
"summarize_log_errors",
"update_maintenance_window",
"update_monitor",
"update_status_page",
"update_status_page_incident"
],
"names_truncated": false,
"sha256": "6657ef764c1265916364b96982a3bd3bca7228960360001b3a7bb489b35c56b6"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T13:51:04.872667+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