Remote MCP · Endpoint

Tribunal TJMS: Cadastro de Pedido de Certidão (1º grau) MCP server

No. Tribunal TJMS: Cadastro de Pedido de Certidão (1º grau) answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://api.mcp.ai/p_tribunal_tjms_pedido_cert

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/tribunal_tjms_pedido_cert-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
64 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Tribunal TJMS: Cadastro de Pedido de Certificate (1º grau), official-source lookup. Platform-hosted,
Repository
https://github.com/mcp-dir/tribunal_tjms_pedido_cert-mcp
Listing
From the official MCP registry (active).
Recent checks of Tribunal TJMS: Cadastro de Pedido de Certidão (1º grau)
CheckedResultHandshake
2 hours agoHandshake completed64 ms
1 day agoHandshake completed38 ms
2 days agoHandshake completed33 ms
3 days agoHandshake completed34 ms
4 days agoHandshake completed47 ms
5 days agoHandshake completed78 ms
7 days agoHandshake completed170 ms
9 days agoHandshake completed84 ms
11 days agoHandshake completed386 ms
14 days agoHandshake completed71 ms
16 days agoHandshake completed54 ms
18 days agoHandshake completed113 ms
20 days agoHandshake completed60 ms
22 days agoHandshake completed141 ms
24 days agoHandshake completed35 ms
26 days agoHandshake completed65 ms
27 days agoHandshake completed78 ms
29 days agoHandshake completed231 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.

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 Tribunal TJMS: Cadastro de Pedido de Certidão (1º grau) and makes no claim about it beyond what these checks measured.