Remote MCP · Endpoint

ECRVSP Processos: Andamento MCP server

No. ECRVSP Processos: Andamento answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://api.mcp.ai/p_ecrvsp_processos_andamento

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/ecrvsp_processos_andamento-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
163 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
ECRVSP Court Cases: Andamento, official-source lookup. Platform-hosted, pay per query with prepaid c
Listing
From the official MCP registry (active).
Recent checks of ECRVSP Processos: Andamento
CheckedResultHandshake
2 hours agoHandshake completed163 ms
1 day agoHandshake completed89 ms
2 days agoHandshake completed86 ms
3 days agoHandshake completed96 ms
4 days agoHandshake completed34 ms
5 days agoHandshake completed42 ms
7 days agoHandshake completed82 ms
8 days agoHandshake completed171 ms
11 days agoHandshake completed46 ms
14 days agoHandshake completed439 ms
16 days agoHandshake completed495 ms
18 days agoHandshake completed60 ms
20 days agoHandshake completed109 ms
22 days agoHandshake completed87 ms
24 days agoHandshake completed73 ms
26 days agoHandshake completed907 ms
27 days agoHandshake completed142 ms
29 days agoHandshake completed59 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.

Listing data comes from the official MCP registry. Glide is not affiliated with ECRVSP Processos: Andamento and makes no claim about it beyond what these checks measured.