Remote MCP · Endpoint

BuildFlow Enterprise Operations MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://base44.app/api/apps/6ab26dc00debf9a25bca5f3e/functions/enterpriseOpsMcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.jgaethle10/buildflow
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
3 tools
Uptime, last 30 days
31.6% from 19 checks
Described by its publisher as
Discover, route, and hand off enterprise operations problems without exposing private records.
Website
https://base44.app/api/apps/6ab26dc00debf9a25bca5f3e/functions/enterpriseOpsAgentRoute
Listing
From the official MCP registry (active).
Recent checks of BuildFlow Enterprise Operations
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
12 hours agoFailed - the server returned an HTTP error—
1 day agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
6 days agoFailed - the server returned an HTTP error—
8 days agoFailed - the server returned an HTTP error—
11 days agoFailed - the server returned an HTTP error—
13 days agoFailed - the server returned an HTTP error—
16 days agoFailed - the server returned an HTTP error—
18 days agoFailed - the server returned an HTTP error—
20 days agoHandshake completed288 ms
22 days agoHandshake completed342 ms
24 days agoHandshake completed386 ms
26 days agoHandshake completed262 ms
28 days agoHandshake completed452 ms
29 days agoHandshake completed515 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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