Remote MCP · Endpoint

AI Flowchart MCP server

No. AI Flowchart answered an MCP handshake 48 minutes ago.

UpLast checked 48 minutes ago

Server URL

https://mcp.aiflowchart.io/mcp

The last check completed an MCP handshake.

Registry name
io.aiflowchart/diagrams
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
650 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Flowcharts, UML/ER diagrams, mind maps, infographics and SOPs as editable, presentable boards
Listing
From the official MCP registry (active).
Recent checks of AI Flowchart
CheckedResultHandshake
48 minutes agoHandshake completed650 ms
10 days agoHandshake completed649 ms
10 days agoHandshake completed656 ms
11 days agoHandshake completed651 ms
12 days agoHandshake completed652 ms
14 days agoHandshake completed660 ms
14 days agoHandshake completed1.84 s
15 days agoHandshake completed1.83 s
17 days agoHandshake completed648 ms
19 days agoHandshake completed660 ms
21 days agoHandshake completed652 ms
24 days agoHandshake completed653 ms
26 days agoHandshake completed655 ms
28 days agoHandshake completed1.81 s

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with AI Flowchart and makes no claim about it beyond what these checks measured.