Remote MCP · Endpoint

PegaRex MCP server

Yes, as of 5 hours ago: the server returned an HTTP error.

DownLast checked 5 hours ago

Server URL

https://pegarex.com.br/api/mcp

The last check failed: the server returned an HTTP error.

Registry name
br.com.pegarex/mcp
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
17 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Search 1.8M+ live Brazilian used-car and motorcycle listings, with FIPE reference prices.
Listing
From the official MCP registry (active).
Recent checks of PegaRex
CheckedResultHandshake
5 hours agoFailed - the server returned an HTTP error—
9 days agoCredentials required—
10 days agoCredentials required—
11 days agoCredentials required—
12 days agoCredentials required—
14 days agoCredentials required—
14 days agoCredentials required—
15 days agoCredentials required—
17 days agoCredentials required—
19 days agoCredentials required—
21 days agoCredentials required—
24 days agoCredentials required—
26 days agoCredentials required—
28 days agoCredentials required—

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 27 responding of 28.

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.