Remote MCP · Endpoint
com.catalogapi/catalogapi MCP server
No. com.catalogapi/catalogapi answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.catalogapi.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.catalogapi/catalogapi
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 445 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Check reward coverage by country, search real catalog items, and ask how CatalogAPI works.
- Website
- https://api.catalogapi.com/
- Repository
- https://github.com/catalogapi/mcp-server
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 445 ms |
| 19 hours ago | Handshake completed | 451 ms |
| 2 days ago | Handshake completed | 425 ms |
| 3 days ago | Handshake completed | 451 ms |
| 4 days ago | Handshake completed | 447 ms |
| 5 days ago | Handshake completed | 442 ms |
| 6 days ago | Handshake completed | 423 ms |
| 8 days ago | Handshake completed | 434 ms |
| 10 days ago | Handshake completed | 415 ms |
| 13 days ago | Handshake completed | 504 ms |
| 15 days ago | Handshake completed | 540 ms |
| 17 days ago | Handshake completed | 588 ms |
| 19 days ago | Handshake completed | 480 ms |
| 21 days ago | Handshake completed | 479 ms |
| 23 days ago | Handshake completed | 469 ms |
| 25 days ago | Handshake completed | 579 ms |
| 27 days ago | Handshake completed | 843 ms |
| 28 days ago | Handshake completed | 555 ms |
| 29 days ago | Handshake completed | 454 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 com.catalogapi/catalogapi and makes no claim about it beyond what these checks measured.