Remote MCP · Endpoint

SEFAZ AM: IPVA MCP server

No. SEFAZ AM: IPVA answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://api.mcp.ai/p_sefaz_am_ipva

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/sefaz_am_ipva-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
49 ms
Tools exposed
7 tools
Uptime, last 30 days
93.8% from 16 checks
Described by its publisher as
SEFAZ AM: IPVA, official-source lookup. Platform-hosted, pay per query with prepaid credit.
Listing
From the official MCP registry (active).
Recent checks of SEFAZ AM: IPVA
CheckedResultHandshake
1 day agoHandshake completed49 ms
3 days agoFailed - the request timed out—
5 days agoHandshake completed32 ms
7 days agoHandshake completed108 ms
8 days agoHandshake completed76 ms
9 days agoHandshake completed89 ms
12 days agoHandshake completed51 ms
13 days agoHandshake completed27 ms
15 days agoHandshake completed218 ms
16 days agoHandshake completed244 ms
18 days agoHandshake completed99 ms
19 days agoHandshake completed146 ms
20 days agoHandshake completed118 ms
20 days agoHandshake completed53 ms
21 days agoHandshake completed50 ms
23 days agoHandshake completed55 ms

The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 15 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 SEFAZ AM: IPVA and makes no claim about it beyond what these checks measured.