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-22T21:39:56.349639+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://roadflow.io/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T21:39:56.349639+00:00",
"registry_status": null,
"subject": {
"id": "io.roadflow/roadflow",
"kind": "mcp"
},
"tools": {
"names": [
"artifacts_apply_json",
"artifacts_create_shared",
"artifacts_discard",
"artifacts_export_json",
"artifacts_get",
"artifacts_get_version",
"artifacts_list_versions",
"artifacts_new",
"artifacts_open_shared",
"artifacts_status",
"model_delete_edge",
"model_delete_observation",
"model_delete_parameter",
"model_discard",
"model_evaluate",
"model_get",
"model_get_parameter",
"model_list_dictionaries",
"model_list_edges",
"model_list_observations",
"model_list_parameters",
"model_new",
"model_open",
"model_patch_project",
"model_status",
"model_upsert_edge",
"model_upsert_observation",
"model_upsert_observations",
"model_upsert_parameter",
"model_upsert_parameters",
"roadflow_apply_json",
"roadflow_apply_markup",
"roadflow_create_shared",
"roadflow_discard",
"roadflow_export_csv",
"roadflow_export_json",
"roadflow_export_markup",
"roadflow_get",
"roadflow_get_version",
"roadflow_list_versions",
"roadflow_new",
"roadflow_open_shared",
"roadflow_status"
],
"names_truncated": false,
"sha256": "ce3725e12d2982640ac055470c6bc83b0b251be64913f0d061e228611141cd1b"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T21:39:56.349639+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