Remote MCP · Endpoint
Recurly MCP by usefulapi MCP server
No. Recurly MCP by usefulapi answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://recurly.usefulapi.io/mcp
The last check completed an MCP handshake.
- Registry name
- io.usefulapi/recurly
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 175 ms
- Tools exposed
- 8 tools
- Uptime, last 30 days
- 38.9% from 18 checks
- Described by its publisher as
- MCP server for Recurly — accounts, subscriptions, invoices, plans; cancel & pause subs.
- Repository
- https://github.com/m190/usefulapi-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 175 ms |
| 2 days ago | Handshake completed | 258 ms |
| 4 days ago | Handshake completed | 221 ms |
| 6 days ago | Handshake completed | 223 ms |
| 7 days ago | Handshake completed | 177 ms |
| 9 days ago | Handshake completed | 56 ms |
| 10 days ago | Failed - the check failed for an unclassified reason | — |
| 11 days ago | Handshake completed | 309 ms |
| 14 days ago | Failed - the check failed for an unclassified reason | — |
| 15 days ago | Failed - the check failed for an unclassified reason | — |
| 17 days ago | Failed - the check failed for an unclassified reason | — |
| 19 days ago | Failed - the check failed for an unclassified reason | — |
| 20 days ago | Failed - the check failed for an unclassified reason | — |
| 21 days ago | Failed - the check failed for an unclassified reason | — |
| 22 days ago | Failed - the check failed for an unclassified reason | — |
| 22 days ago | Failed - the check failed for an unclassified reason | — |
| 23 days ago | Failed - the check failed for an unclassified reason | — |
| 25 days ago | Failed - the check failed for an unclassified reason | — |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 7 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 Recurly MCP by usefulapi and makes no claim about it beyond what these checks measured.