Remote MCP · Endpoint

Paraíso MCP server

No. Paraíso answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://paraiso.sampa.br/mcp

The last check completed an MCP handshake.

Registry name
io.github.junoventures/paraiso-sampa-br
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
235 ms
Tools exposed
26 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Paraíso — neighborhood directory: local places, events, menus, offers, and services.
Listing
From the official MCP registry (active).
Recent checks of Paraíso
CheckedResultHandshake
1 hour agoHandshake completed235 ms
2 days agoHandshake completed95 ms
4 days agoHandshake completed92 ms
5 days agoHandshake completed87 ms
7 days agoHandshake completed86 ms
8 days agoHandshake completed99 ms
9 days agoHandshake completed94 ms
12 days agoHandshake completed90 ms
13 days agoHandshake completed100 ms
15 days agoHandshake completed201 ms
17 days agoHandshake completed201 ms
18 days agoHandshake completed95 ms
19 days agoHandshake completed97 ms
20 days agoHandshake completed116 ms
20 days agoHandshake completed213 ms
21 days agoHandshake completed191 ms
23 days agoHandshake completed85 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 Paraíso and makes no claim about it beyond what these checks measured.