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-22T09:55:42.105333+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.seaweb.tech/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T09:55:42.105333+00:00",
"registry_status": null,
"subject": {
"id": "tech.seaweb/seaweb",
"kind": "mcp"
},
"tools": {
"names": [
"agent_job_status",
"build_dataset",
"cancel_agent_job",
"compare_search",
"delete_disruption_webhook",
"delete_standing_query",
"extract_url",
"filter_restaurants",
"filter_salons",
"get_camera_visibility",
"get_details",
"get_disruption_event",
"get_disruptions",
"get_entity",
"get_hours",
"get_menu",
"get_restaurant",
"get_salon",
"get_services",
"get_site_skill",
"get_spot_conditions",
"list_disruption_events",
"list_disruption_webhooks",
"list_sources",
"list_standing_queries",
"list_verticals",
"log_outcome",
"recall",
"register_disruption_webhook",
"register_standing_query",
"remember",
"research",
"research_status",
"resolve_geo",
"search",
"search_destination_sentiment",
"search_restaurants",
"search_salons",
"search_web",
"submit_feedback",
"teamwork_preview",
"travel_health",
"vote_comparison"
],
"names_truncated": false,
"sha256": "35ee8311f6469715bc6e4896569b4516c1a43230fa0826bbdf1f18fa82c01784"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T09:55:42.105333+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