Remote MCP · Endpoint
Amberflo MCP by usefulapi MCP server
No. Amberflo MCP by usefulapi answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://amberflo.usefulapi.io/mcp
The last check completed an MCP handshake.
- Registry name
- io.usefulapi/amberflo
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 206 ms
- Tools exposed
- 14 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Query and manage Amberflo metering & billing: customers, meters, usage, plans, invoices, prepaid.
- Repository
- https://github.com/m190/usefulapi-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 206 ms |
| 2 days ago | Handshake completed | 266 ms |
| 4 days ago | Handshake completed | 242 ms |
| 6 days ago | Handshake completed | 188 ms |
| 7 days ago | Handshake completed | 211 ms |
| 9 days ago | Handshake completed | 327 ms |
| 10 days ago | Handshake completed | 520 ms |
| 11 days ago | Handshake completed | 216 ms |
| 14 days ago | Handshake completed | 158 ms |
| 15 days ago | Handshake completed | 178 ms |
| 17 days ago | Handshake completed | 225 ms |
| 19 days ago | Handshake completed | 190 ms |
| 20 days ago | Handshake completed | 165 ms |
| 21 days ago | Handshake completed | 136 ms |
| 22 days ago | Handshake completed | 260 ms |
| 22 days ago | Handshake completed | 170 ms |
| 23 days ago | Handshake completed | 236 ms |
| 25 days ago | Handshake completed | 175 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 18 responding of 18.
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 Amberflo MCP by usefulapi and makes no claim about it beyond what these checks measured.