Is ai.flowcastle/flowcastle up? Live MCP status

Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.

Endpointhttps://api.flowcastle.ai/api/mcp
Page built

One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.

Live status every few hours: Wellknown

Email me when this server changes

That was one look. To hear when it stops answering or its tools change, leave an address.

Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.

Monthly census, 6 October 2026

The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).

Agent discovery documents at this origin

A2A agent cardNot published (HTTP 404).
/.well-known/agent-card.json
MCP server card (SEP-2127)Not published (HTTP 404).
https://api.flowcastle.ai/api/mcp/server-card
MCP server card (SEP-1649 location)Not published (HTTP 404).
/.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026
Web Bot Auth key directoryNot published (HTTP 404).
/.well-known/http-message-signatures-directory

Read at https://api.flowcastle.ai with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.

Tool changes between snapshots

In the 2026-10 snapshot it listed 51 tools: 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_variable_context, get_website_import, get_workspace_summary, import_website_knowledge, install_module, list_applications, list_broadcasts, list_contact_tags, list_contacts, list_event_contacts, list_follow_up_tasks, list_pulse_items, list_telegram_operations, list_watched_groups, query_flow_logs, read_messages, run_flow_autotest, 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, validate_actions.

Its tools changed between 2026-09 and 2026-10:

Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.

The listing

Registry nameai.flowcastle/flowcastle
Endpointhttps://api.flowcastle.ai/api/mcp
Publisher repositorynot known: the registry did not return this listing within 4 seconds

Also

The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt

Free, no key, no signup. Terms · Privacy