Remote MCP · Endpoint

SEFAZ GO: IPVA MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://api.mcp.ai/p_sefaz_go_ipva

The last check failed: the server returned an HTTP error.

Registry name
io.github.mcp-dir/sefaz_go_ipva-mcp
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
7 tools
Uptime, last 30 days
83.3% from 18 checks
Described by its publisher as
SEFAZ GO: IPVA, official-source lookup. Platform-hosted, pay per query with prepaid credit.
Repository
https://github.com/mcp-dir/sefaz_go_ipva-mcp
Listing
From the official MCP registry (active).
Recent checks of SEFAZ GO: IPVA
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
1 day agoHandshake completed104 ms
2 days agoHandshake completed91 ms
3 days agoFailed - the request timed out—
4 days agoHandshake completed30 ms
5 days agoHandshake completed47 ms
6 days agoHandshake completed63 ms
8 days agoHandshake completed134 ms
11 days agoHandshake completed38 ms
13 days agoHandshake completed1.07 s
16 days agoHandshake completed601 ms
18 days agoHandshake completed231 ms
20 days agoHandshake completed45 ms
22 days agoHandshake completed52 ms
24 days agoFailed - the request timed out—
26 days agoHandshake completed32 ms
27 days agoHandshake completed132 ms
29 days agoHandshake completed92 ms

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