Remote MCP · Endpoint
PegaRex MCP server
No — it is up, but it requires credentials. PegaRex answered 1 hour ago with an authentication challenge rather than a session.
Auth requiredLast checked 1 hour ago
Server URL
https://pegarex.com.br/api/mcp
The endpoint is answering and asked us for credentials. That is a working server, not an outage.
- Registry name
- br.com.pegarex/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 17 tools
- Uptime, last 30 days
- 100% from 15 checks
- Described by its publisher as
- Search 1.8M+ live Brazilian used-car and motorcycle listings, with FIPE reference prices.
- Website
- https://pegarex.com.br/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Credentials required | — |
| 1 day ago | Handshake completed | 698 ms |
| 4 days ago | Handshake completed | 412 ms |
| 6 days ago | Handshake completed | 378 ms |
| 7 days ago | Handshake completed | 496 ms |
| 9 days ago | Handshake completed | 404 ms |
| 10 days ago | Handshake completed | 376 ms |
| 11 days ago | Handshake completed | 366 ms |
| 14 days ago | Handshake completed | 486 ms |
| 15 days ago | Handshake completed | 485 ms |
| 17 days ago | Handshake completed | 494 ms |
| 18 days ago | Handshake completed | 487 ms |
| 20 days ago | Handshake completed | 367 ms |
| 21 days ago | Handshake completed | 381 ms |
| 22 days ago | Handshake completed | 535 ms |
The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.
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 PegaRex and makes no claim about it beyond what these checks measured.