Remote MCP · Endpoint
Customer.io MCP by usefulapi MCP server
No. Customer.io MCP by usefulapi answered an MCP handshake 1 day ago.
UpLast checked 1 day ago
Server URL
https://customerio.usefulapi.io/mcp
The last check completed an MCP handshake.
- Registry name
- io.usefulapi/customerio
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 133 ms
- Tools exposed
- 13 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Query people, segments, campaigns, and message deliveries; send transactional email or broadcasts.
- Repository
- https://github.com/m190/usefulapi-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 day ago | Handshake completed | 133 ms |
| 3 days ago | Handshake completed | 187 ms |
| 5 days ago | Handshake completed | 176 ms |
| 7 days ago | Handshake completed | 177 ms |
| 9 days ago | Handshake completed | 150 ms |
| 10 days ago | Handshake completed | 362 ms |
| 11 days ago | Handshake completed | 318 ms |
| 14 days ago | Handshake completed | 202 ms |
| 15 days ago | Handshake completed | 185 ms |
| 17 days ago | Handshake completed | 295 ms |
| 18 days ago | Handshake completed | 242 ms |
| 19 days ago | Handshake completed | 154 ms |
| 21 days ago | Handshake completed | 175 ms |
| 22 days ago | Handshake completed | 187 ms |
| 22 days ago | Handshake completed | 155 ms |
| 23 days ago | Handshake completed | 370 ms |
| 24 days ago | Handshake completed | 165 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 Customer.io MCP by usefulapi and makes no claim about it beyond what these checks measured.