Remote MCP · Endpoint

Certidão MPF MCP server

No. Certidão MPF answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://api.mcp.ai/p_mpf_certidao

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/mpf_certidao-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
46 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Issues the clearance certificate from the Federal Public Prosecutor's Office (MPF) for a person or c
Listing
From the official MCP registry (active).
Recent checks of Certidão MPF
CheckedResultHandshake
1 day agoHandshake completed46 ms
3 days agoHandshake completed129 ms
5 days agoHandshake completed381 ms
7 days agoHandshake completed1.04 s
8 days agoHandshake completed175 ms
9 days agoHandshake completed53 ms
11 days agoHandshake completed526 ms
13 days agoHandshake completed52 ms
15 days agoHandshake completed90 ms
16 days agoHandshake completed278 ms
18 days agoHandshake completed114 ms
19 days agoHandshake completed116 ms
20 days agoHandshake completed652 ms
20 days agoHandshake completed39 ms
21 days agoHandshake completed57 ms
22 days agoHandshake completed118 ms

The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

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 Certidão MPF and makes no claim about it beyond what these checks measured.