Remote MCP · Endpoint

SEFAZ SE: NFC-e MCP server

No. SEFAZ SE: NFC-e answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.mcp.ai/p_sefaz_se_nfce

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/sefaz_se_nfce-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
59 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
SEFAZ SE: NFC-e, official-source lookup. Platform-hosted, pay per query with prepaid credit.
Repository
https://github.com/mcp-dir/sefaz_se_nfce-mcp
Listing
From the official MCP registry (active).
Recent checks of SEFAZ SE: NFC-e
CheckedResultHandshake
1 hour agoHandshake completed59 ms
2 days agoHandshake completed4.48 s
4 days agoHandshake completed245 ms
5 days agoHandshake completed508 ms
7 days agoHandshake completed37 ms
8 days agoHandshake completed245 ms
9 days agoHandshake completed126 ms
12 days agoHandshake completed73 ms
14 days agoHandshake completed615 ms
15 days agoHandshake completed140 ms
17 days agoHandshake completed64 ms
18 days agoHandshake completed70 ms
19 days agoHandshake completed50 ms
20 days agoHandshake completed272 ms
20 days agoHandshake completed111 ms
22 days agoHandshake completed878 ms
23 days agoHandshake completed809 ms

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

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