Remote MCP · Endpoint

JUCESP: REDESIM, Acompanhamento de Protocolo MCP server

No. JUCESP: REDESIM, Acompanhamento de Protocolo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.mcp.ai/p_jucesp_redesim_protocolo

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/jucesp_redesim_protocolo-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
2.90 s
Tools exposed
7 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Tracks a REDESIM protocol at JUCESP (company opening, change or closure). Platform-hosted, no creden
Repository
https://github.com/mcp-dir/jucesp_redesim_protocolo-mcp
Listing
From the official MCP registry (active).
Recent checks of JUCESP: REDESIM, Acompanhamento de Protocolo
CheckedResultHandshake
1 hour agoHandshake completed2.90 s
1 day agoHandshake completed69 ms
2 days agoHandshake completed48 ms
3 days agoHandshake completed43 ms
4 days agoHandshake completed49 ms
5 days agoHandshake completed35 ms
6 days agoHandshake completed355 ms
8 days agoHandshake completed80 ms
11 days agoHandshake completed32 ms
14 days agoHandshake completed84 ms
16 days agoHandshake completed44 ms
18 days agoHandshake completed45 ms
20 days agoHandshake completed148 ms
22 days agoHandshake completed79 ms
24 days agoHandshake completed78 ms
26 days agoHandshake completed769 ms
27 days agoHandshake completed106 ms
29 days agoHandshake completed119 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with JUCESP: REDESIM, Acompanhamento de Protocolo and makes no claim about it beyond what these checks measured.