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-20T23:03:12.376209+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://connect.clueso.io/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-20T23:03:12.376209+00:00",
"registry_status": null,
"subject": {
"id": "io.clueso/video",
"kind": "mcp"
},
"tools": {
"names": [
"add_article_media",
"add_audio",
"add_clips",
"add_comment",
"add_elements",
"add_sync_point",
"analyze_audio",
"auto_sync",
"captions",
"check_uploads",
"create_clueprint",
"create_folder",
"create_project",
"duplicate_clip",
"duplicate_project",
"edit_animation",
"export_project",
"extract_audio",
"find",
"generate_media",
"get_article",
"get_clip",
"get_clueprint",
"get_comments",
"get_design_guide",
"get_element_schema",
"get_embed",
"get_export",
"get_project",
"get_recording_activity",
"get_script_job",
"read_animation",
"record_screen",
"remove_clip",
"remove_elements",
"remove_from_project",
"reorder_elements",
"run_script",
"set_voice",
"split_clip",
"switch_workspace",
"update_article",
"update_article_media",
"update_audio",
"update_clips",
"update_clueprint",
"update_elements",
"update_groups",
"update_project",
"upload_file",
"voiceover_batch"
],
"names_truncated": false,
"sha256": "37e6f57e9637cde1e21b6f20ec8a7c24401308ec78f6a521bb9a33d2ee33b784"
},
"tools_complete": true,
"tools_observed_at": "2026-10-20T23:03:12.376209+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