Remote MCP · Endpoint

MTE: Processos por Empregador MCP server

No. MTE: Processos por Empregador answered an MCP handshake 2 hours ago.

UpLast checked 2 hours 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
421 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
MTE: Court Cases por Empregador, official-source lookup. Platform-hosted, pay per query with prepaid
Repository
https://github.com/mcp-dir/mte_processo_empregador-mcp
Listing
From the official MCP registry (active).
Recent checks of MTE: Processos por Empregador
CheckedResultHandshake
2 hours agoHandshake completed421 ms
2 days agoHandshake completed59 ms
4 days agoHandshake completed35 ms
5 days agoHandshake completed90 ms
7 days agoHandshake completed91 ms
8 days agoHandshake completed235 ms
9 days agoHandshake completed2.78 s
12 days agoHandshake completed167 ms
14 days agoHandshake completed51 ms
15 days agoHandshake completed2.78 s
17 days agoHandshake completed62 ms
18 days agoHandshake completed58 ms
19 days agoHandshake completed1.00 s
20 days agoHandshake completed71 ms
20 days agoHandshake completed51 ms
21 days agoHandshake completed123 ms
23 days agoHandshake completed69 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 MTE: Processos por Empregador and makes no claim about it beyond what these checks measured.