Remote MCP · Endpoint

EGOS (público) MCP server

No. EGOS (público) answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://mcp.egos.ia.br/publico/mcp

The last check completed an MCP handshake.

Registry name
io.github.enioxt/publico
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
459 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Diagnóstico 'cabe IA?' por regra fixa, capacidades do EGOS com prova, pesquisa pública. Sem senha.
Listing
From the official MCP registry (active).
Recent checks of EGOS (público)
CheckedResultHandshake
34 minutes agoHandshake completed459 ms
9 days agoHandshake completed335 ms
10 days agoHandshake completed332 ms
11 days agoHandshake completed339 ms
12 days agoHandshake completed498 ms
14 days agoHandshake completed337 ms
14 days agoHandshake completed358 ms
15 days agoHandshake completed492 ms
17 days agoHandshake completed332 ms
19 days agoHandshake completed331 ms
21 days agoHandshake completed337 ms
24 days agoHandshake completed363 ms
26 days agoHandshake completed336 ms
28 days agoHandshake completed326 ms

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

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 EGOS (público) and makes no claim about it beyond what these checks measured.