Remote MCP · Endpoint

Flowie MCP server

No. Flowie answered an MCP handshake 59 minutes ago.

UpLast checked 59 minutes ago

Server URL

https://get-flowie.com/mcp

The last check completed an MCP handshake.

Registry name
com.get-flowie/website
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
97 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Ask about Flowie: invoicing in 150 countries via Sovos, order-to-cash, procure-to-pay, SRM.
Listing
From the official MCP registry (active).
Recent checks of Flowie
CheckedResultHandshake
59 minutes agoHandshake completed97 ms
9 days agoHandshake completed112 ms
10 days agoHandshake completed132 ms
11 days agoHandshake completed72 ms
12 days agoHandshake completed80 ms
14 days agoHandshake completed146 ms
14 days agoHandshake completed101 ms
15 days agoHandshake completed103 ms
17 days agoHandshake completed194 ms
19 days agoHandshake completed151 ms
21 days agoHandshake completed85 ms
24 days agoHandshake completed130 ms
26 days agoHandshake completed227 ms

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

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 Flowie and makes no claim about it beyond what these checks measured.