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-22T00:26:36.947565+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.flowcastle.ai/api/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T00:26:36.947565+00:00",
"registry_status": null,
"subject": {
"id": "ai.flowcastle/flowcastle",
"kind": "mcp"
},
"tools": {
"names": [
"apply_actions",
"create_application",
"create_contact",
"create_follow_up_task",
"deploy_application",
"execute_telegram_operation",
"get_action_schema",
"get_application_context",
"get_block_details",
"get_broadcast_analytics",
"get_broadcast_details",
"get_contact",
"get_contact_activity",
"get_design_guidelines",
"get_flow_analytics",
"get_flow_context",
"get_flow_example",
"get_funnel_analytics",
"get_module_catalog",
"get_module_details",
"get_pulse_item",
"get_survey_results",
"get_telegram_operation",
"get_tribute_setup",
"get_variable_context",
"get_website_import",
"get_workspace_summary",
"import_website_knowledge",
"install_module",
"list_applications",
"list_bot_chats",
"list_broadcasts",
"list_contact_tags",
"list_contacts",
"list_event_contacts",
"list_follow_up_tasks",
"list_pulse_items",
"list_releases",
"list_telegram_operations",
"list_tribute_account_products",
"list_tribute_purchases",
"list_watched_groups",
"query_flow_logs",
"read_messages",
"restore_release",
"retry_tribute_delivery",
"run_flow_autotest",
"save_tribute_product",
"search_flow_examples",
"search_flows",
"send_flow_to_contacts",
"send_message",
"set_watched_groups",
"sync_dialog_contacts",
"update_application",
"update_contact",
"update_follow_up_task",
"update_pulse_item",
"update_tribute_connection",
"validate_actions"
],
"names_truncated": false,
"sha256": "75d51c40310ee67cc223032a11563cacd0729fb4cd9eee20c631ecfc24f69a45"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T00:26:36.947565+00:00",
"version": "1.0.0"
}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