Remote MCP · Endpoint

Liberdade MCP server

No. Liberdade answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://liberdade.sampa.br/mcp

The last check completed an MCP handshake.

Registry name
io.github.junoventures/liberdade-sampa-br
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
109 ms
Tools exposed
28 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Bairro da Liberdade em São Paulo.
Listing
From the official MCP registry (active).
Recent checks of Liberdade
CheckedResultHandshake
1 hour agoHandshake completed109 ms
2 days agoHandshake completed80 ms
4 days agoHandshake completed99 ms
5 days agoHandshake completed101 ms
7 days agoHandshake completed106 ms
8 days agoHandshake completed113 ms
9 days agoHandshake completed71 ms
12 days agoHandshake completed235 ms
13 days agoHandshake completed113 ms
15 days agoHandshake completed713 ms
17 days agoHandshake completed75 ms
18 days agoHandshake completed73 ms
19 days agoHandshake completed94 ms
20 days agoHandshake completed114 ms
20 days agoHandshake completed101 ms
21 days agoHandshake completed78 ms
23 days agoHandshake completed117 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 Liberdade and makes no claim about it beyond what these checks measured.