Remote MCP · Endpoint

Dataprev: Fator Acidentário de Prevenção (FAP) MCP server

No. Dataprev: Fator Acidentário de Prevenção (FAP) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.mcp.ai/p_dataprev_fap

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/dataprev_fap-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
104 ms
Tools exposed
7 tools
Uptime, last 30 days
94.1% from 17 checks
Described by its publisher as
Dataprev: Fator Acidentário de Prevenção (FAP), official-source lookup. Platform-hosted, pay per que
Listing
From the official MCP registry (active).
Recent checks of Dataprev: Fator Acidentário de Prevenção (FAP)
CheckedResultHandshake
1 hour agoHandshake completed104 ms
2 days agoHandshake completed336 ms
4 days agoHandshake completed86 ms
5 days agoHandshake completed110 ms
7 days agoHandshake completed76 ms
8 days agoHandshake completed191 ms
9 days agoHandshake completed125 ms
12 days agoHandshake completed220 ms
14 days agoHandshake completed157 ms
15 days agoFailed - the server returned an HTTP error—
17 days agoHandshake completed83 ms
18 days agoHandshake completed35 ms
19 days agoHandshake completed72 ms
20 days agoHandshake completed69 ms
20 days agoHandshake completed80 ms
21 days agoHandshake completed143 ms
23 days agoHandshake completed105 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 16 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.

Listing data comes from the official MCP registry. Glide is not affiliated with Dataprev: Fator Acidentário de Prevenção (FAP) and makes no claim about it beyond what these checks measured.