Remote MCP · Endpoint
Tribunal TRF5: Processo MCP server
No. Tribunal TRF5: Processo answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://api.mcp.ai/p_tribunal_trf5_processo
The last check completed an MCP handshake.
- Registry name
- io.github.mcp-dir/tribunal_trf5_processo-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 1.10 s
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Tribunal TRF5: Court Case, official-source lookup. Platform-hosted, pay per query with prepaid credi
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 1.10 s |
| 23 hours ago | Handshake completed | 243 ms |
| 2 days ago | Handshake completed | 34 ms |
| 3 days ago | Handshake completed | 818 ms |
| 4 days ago | Handshake completed | 33 ms |
| 5 days ago | Handshake completed | 34 ms |
| 6 days ago | Handshake completed | 197 ms |
| 8 days ago | Handshake completed | 282 ms |
| 11 days ago | Handshake completed | 137 ms |
| 13 days ago | Handshake completed | 62 ms |
| 16 days ago | Handshake completed | 107 ms |
| 18 days ago | Handshake completed | 274 ms |
| 20 days ago | Handshake completed | 29 ms |
| 22 days ago | Handshake completed | 68 ms |
| 24 days ago | Handshake completed | 1.14 s |
| 26 days ago | Handshake completed | 69 ms |
| 27 days ago | Handshake completed | 54 ms |
| 29 days ago | Handshake completed | 48 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 Tribunal TRF5: Processo and makes no claim about it beyond what these checks measured.