Remote MCP · Endpoint

SEFAZ MS: NFC-e MCP server

No. SEFAZ MS: NFC-e answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://api.mcp.ai/p_sefaz_ms_nfce

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/sefaz_ms_nfce-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
134 ms
Tools exposed
7 tools
Uptime, last 30 days
88.9% from 18 checks
Described by its publisher as
SEFAZ MS: NFC-e, official-source lookup. Platform-hosted, pay per query with prepaid credit.
Repository
https://github.com/mcp-dir/sefaz_ms_nfce-mcp
Listing
From the official MCP registry (active).
Recent checks of SEFAZ MS: NFC-e
CheckedResultHandshake
9 hours agoHandshake completed134 ms
1 day agoHandshake completed211 ms
3 days agoFailed - the request timed out—
3 days agoHandshake completed103 ms
4 days agoHandshake completed35 ms
6 days agoHandshake completed385 ms
8 days agoHandshake completed56 ms
10 days agoHandshake completed34 ms
13 days agoHandshake completed173 ms
15 days agoHandshake completed50 ms
17 days agoHandshake completed48 ms
19 days agoHandshake completed59 ms
21 days agoHandshake completed46 ms
23 days agoFailed - the request timed out—
25 days agoHandshake completed62 ms
27 days agoHandshake completed225 ms
28 days agoHandshake completed84 ms
29 days agoHandshake completed65 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 MS: NFC-e and makes no claim about it beyond what these checks measured.