Remote MCP · Endpoint
SEFAZ PI: IPVA MCP server
No. SEFAZ PI: IPVA answered an MCP handshake 9 hours ago.
UpLast checked 9 hours ago
Server URL
https://api.mcp.ai/p_sefaz_pi_ipva
The last check completed an MCP handshake.
- Registry name
- io.github.mcp-dir/sefaz_pi_ipva-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 127 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 83.3% from 18 checks
- Described by its publisher as
- SEFAZ PI: IPVA, official-source lookup. Platform-hosted, pay per query with prepaid credit.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 9 hours ago | Handshake completed | 127 ms |
| 1 day ago | Handshake completed | 52 ms |
| 3 days ago | Failed - the request timed out | — |
| 3 days ago | Handshake completed | 51 ms |
| 4 days ago | Handshake completed | 42 ms |
| 6 days ago | Handshake completed | 198 ms |
| 8 days ago | Handshake completed | 120 ms |
| 10 days ago | Handshake completed | 38 ms |
| 13 days ago | Failed - the request timed out | — |
| 15 days ago | Handshake completed | 77 ms |
| 17 days ago | Handshake completed | 80 ms |
| 19 days ago | Handshake completed | 109 ms |
| 21 days ago | Handshake completed | 46 ms |
| 23 days ago | Failed - the request timed out | — |
| 25 days ago | Handshake completed | 29 ms |
| 27 days ago | Handshake completed | 119 ms |
| 28 days ago | Handshake completed | 99 ms |
| 29 days ago | Handshake completed | 126 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 25 responding of 28.
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 SEFAZ PI: IPVA and makes no claim about it beyond what these checks measured.