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:09.830767+00:00 · State: auth_required
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": "required",
"availability": "auth_required",
"endpoint": "https://mcp.lastping.dev",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-30T11:39:09.830767+00:00",
"registry_status": null,
"subject": {
"id": "dev.lastping/lastping",
"kind": "mcp"
},
"tools": {
"names": [
"add_incident_note",
"adopt_discovered_agent",
"create_api_key",
"create_destination",
"create_ingest_key",
"create_monitor",
"create_status_page",
"declare_run_expectations",
"delete_agent",
"delete_destination",
"delete_monitor",
"delete_route",
"delete_status_page",
"discover_monitors_reconcile",
"export_terraform",
"get_agent",
"get_agent_dependencies",
"get_agent_usage",
"get_alert_templates",
"get_incident",
"get_monitor",
"get_ping_instructions",
"get_run",
"get_run_history",
"get_trace_diagnostics",
"get_trace_setup",
"list_agents",
"list_api_keys",
"list_deliveries",
"list_dependencies",
"list_destinations",
"list_discovered_agents",
"list_incidents",
"list_monitors",
"list_open_incidents",
"list_runs",
"list_status_pages",
"pause_monitor",
"regenerate_api_key",
"register_agent",
"resume_monitor",
"revoke_api_key",
"set_alert_template",
"set_route",
"snooze_monitor",
"test_destination",
"update_agent",
"update_destination",
"update_monitor",
"update_status_page"
],
"names_truncated": false,
"sha256": "fea6d5b0852c02856b4592c4015bbe2a766c98b89478d157cc5cf551bc252c1e"
},
"tools_complete": true,
"tools_observed_at": "2026-10-30T11:39:09.830767+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