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-21T08:06:05.181476+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://eventchat-events-mcp-production.up.railway.app/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-21T08:06:05.181476+00:00",
"registry_status": null,
"subject": {
"id": "xyz.urbanplayground/events",
"kind": "mcp"
},
"tools": {
"names": [
"add_to_dizko_plan",
"bin_event",
"create_event_calendar_file",
"create_event_preference_profile",
"delete_event_preferences",
"find_scene_entities",
"get_artist",
"get_artist_events",
"get_artist_page",
"get_city_pulse",
"get_daily_roundup",
"get_dizko_onboarding",
"get_event",
"get_event_feedback_prompt",
"get_event_preferences",
"get_event_search_followups",
"get_preference_onboarding",
"get_taste_profile",
"get_ticket_offers",
"get_ticket_purchase_policy",
"get_venue",
"list_cities",
"plan_night",
"purchase_ticket_order",
"quote_ticket_order",
"recommend_events",
"recommend_events_for_user",
"record_event_feedback",
"save_event",
"save_event_preferences",
"search_events"
],
"names_truncated": false,
"sha256": "5502caa1d8feb3ab5301de8d0889620e4583f3f24732163b86771b0f99bd1c5f"
},
"tools_complete": true,
"tools_observed_at": "2026-10-21T08:06:05.181476+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