Remote MCP · Endpoint

ECRVSP Processos: Andamento MCP server

No. ECRVSP Processos: Andamento answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
109 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
ECRVSP Court Cases: Andamento, official-source lookup. Platform-hosted, pay per query with prepaid c
Repository
https://github.com/mcp-dir/ecrvsp_processos_andamento-mcp
Listing
From the official MCP registry (active).
Recent checks of ECRVSP Processos: Andamento
CheckedResultHandshake
1 hour agoHandshake completed109 ms
2 days agoHandshake completed87 ms
4 days agoHandshake completed73 ms
5 days agoHandshake completed907 ms
7 days agoHandshake completed142 ms
8 days agoHandshake completed59 ms
9 days agoHandshake completed94 ms
12 days agoHandshake completed83 ms
14 days agoHandshake completed142 ms
15 days agoHandshake completed53 ms
17 days agoHandshake completed56 ms
18 days agoHandshake completed33 ms
19 days agoHandshake completed68 ms
20 days agoHandshake completed103 ms
20 days agoHandshake completed109 ms
21 days agoHandshake completed78 ms
23 days agoHandshake completed128 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.

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 ECRVSP Processos: Andamento and makes no claim about it beyond what these checks measured.