Remote MCP · Endpoint

SEFAZ SC: NFC-e MCP server

No. SEFAZ SC: NFC-e answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://api.mcp.ai/p_sefaz_sc_nfce

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/sefaz_sc_nfce-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
802 ms
Tools exposed
7 tools
Uptime, last 30 days
88.9% from 18 checks
Described by its publisher as
SEFAZ SC: NFC-e, official-source lookup. Platform-hosted, pay per query with prepaid credit.
Repository
https://github.com/mcp-dir/sefaz_sc_nfce-mcp
Listing
From the official MCP registry (active).
Recent checks of SEFAZ SC: NFC-e
CheckedResultHandshake
5 hours agoHandshake completed802 ms
1 day agoHandshake completed43 ms
3 days agoFailed - the request timed out—
3 days agoHandshake completed83 ms
4 days agoHandshake completed41 ms
6 days agoHandshake completed132 ms
8 days agoHandshake completed47 ms
10 days agoHandshake completed41 ms
13 days agoHandshake completed2.00 s
15 days agoHandshake completed99 ms
17 days agoHandshake completed54 ms
19 days agoHandshake completed41 ms
21 days agoHandshake completed44 ms
23 days agoFailed - the request timed out—
25 days agoHandshake completed25 ms
27 days agoHandshake completed1.33 s
28 days agoHandshake completed78 ms
29 days agoHandshake completed61 ms

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

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