Remote MCP · Endpoint

SEFAZ AC: NFC-e MCP server

No. SEFAZ AC: NFC-e answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://api.mcp.ai/p_sefaz_ac_nfce

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/sefaz_ac_nfce-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
45 ms
Tools exposed
7 tools
Uptime, last 30 days
93.8% from 16 checks
Described by its publisher as
SEFAZ AC: NFC-e, official-source lookup. Platform-hosted, pay per query with prepaid credit.
Repository
https://github.com/mcp-dir/sefaz_ac_nfce-mcp
Listing
From the official MCP registry (active).
Recent checks of SEFAZ AC: NFC-e
CheckedResultHandshake
1 day agoHandshake completed45 ms
3 days agoFailed - the request timed out—
5 days agoHandshake completed39 ms
7 days agoHandshake completed79 ms
8 days agoHandshake completed60 ms
9 days agoHandshake completed100 ms
11 days agoHandshake completed79 ms
13 days agoHandshake completed29 ms
15 days agoHandshake completed87 ms
16 days agoHandshake completed278 ms
18 days agoHandshake completed90 ms
19 days agoHandshake completed244 ms
20 days agoHandshake completed135 ms
20 days agoHandshake completed56 ms
21 days agoHandshake completed72 ms
22 days agoHandshake completed33 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.

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 AC: NFC-e and makes no claim about it beyond what these checks measured.