Remote MCP · Endpoint

MTE: Processos por Empregador MCP server

No. MTE: Processos por Empregador answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.mcp.ai/p_mte_processo_empregador

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/mte_processo_empregador-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
70 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
MTE: Court Cases por Empregador, official-source lookup. Platform-hosted, pay per query with prepaid
Listing
From the official MCP registry (active).
Recent checks of MTE: Processos por Empregador
CheckedResultHandshake
1 hour agoHandshake completed70 ms
1 day agoHandshake completed51 ms
2 days agoHandshake completed43 ms
3 days agoHandshake completed50 ms
4 days agoHandshake completed122 ms
5 days agoHandshake completed38 ms
6 days agoHandshake completed259 ms
9 days agoHandshake completed68 ms
11 days agoHandshake completed37 ms
14 days agoHandshake completed70 ms
16 days agoHandshake completed48 ms
18 days agoHandshake completed69 ms
20 days agoHandshake completed421 ms
22 days agoHandshake completed59 ms
24 days agoHandshake completed35 ms
26 days agoHandshake completed90 ms
28 days agoHandshake completed91 ms
29 days agoHandshake completed235 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 MTE: Processos por Empregador and makes no claim about it beyond what these checks measured.