Remote MCP · Endpoint
io.usefulapi/autumn MCP server
Yes, as of 22 minutes ago: the check failed for an unclassified reason.
DownLast checked 22 minutes ago
Server URL
https://autumn.usefulapi.io/mcp
The last check failed: the check failed for an unclassified reason.
- Registry name
- io.usefulapi/autumn
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- Not measured yet
- Uptime, last 30 days
- 40.0% from 5 checks
- Described by its publisher as
- MCP server for Autumn — read customers, plans, balances & invoices; track usage and attach plans.
- Repository
- https://github.com/m190/usefulapi-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 22 minutes ago | Failed - the check failed for an unclassified reason | — |
| 1 day ago | Handshake completed | 167 ms |
| 1 day ago | Failed - the check failed for an unclassified reason | — |
| 2 days ago | Handshake completed | 244 ms |
| 3 days ago | Failed - the check failed for an unclassified reason | — |
The last 5 checks. Full history is kept for 30 days; the all-time counter stands at 2 responding of 5.
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 io.usefulapi/autumn and makes no claim about it beyond what these checks measured.