Remote MCP · Endpoint

Eleições 2026: Dados Públicos do TSE MCP server

No. Eleições 2026: Dados Públicos do TSE answered an MCP handshake 37 minutes ago.

UpLast checked 37 minutes ago

Server URL

https://api.mcp.ai/p_eleicoes

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/eleicoes-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
113 ms
Tools exposed
21 tools
Uptime, last 30 days
91.7% from 12 checks
Described by its publisher as
Brazil 2026 election data from the TSE: ballot box reports, logs, results, SHA-256 and source link.
Listing
From the official MCP registry (active).
Recent checks of Eleições 2026: Dados Públicos do TSE
CheckedResultHandshake
37 minutes agoHandshake completed113 ms
4 days agoHandshake completed272 ms
7 days agoHandshake completed8.87 s
16 days agoHandshake completed1.51 s
16 days agoHandshake completed79 ms
18 days agoHandshake completed1.68 s
19 days agoHandshake completed130 ms
20 days agoHandshake completed76 ms
21 days agoHandshake completed2.59 s
22 days agoHandshake completed1.49 s
23 days agoHandshake completed99 ms
26 days agoFailed - the request timed out—

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

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 Eleições 2026: Dados Públicos do TSE and makes no claim about it beyond what these checks measured.