Remote MCP · Endpoint

SEFAZ MT: NFC-e MCP server

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

UpLast checked 1 hour ago

Server URL

https://api.mcp.ai/p_sefaz_mt_nfce

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/sefaz_mt_nfce-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
48 ms
Tools exposed
7 tools
Uptime, last 30 days
88.9% from 18 checks
Described by its publisher as
SEFAZ MT: NFC-e, official-source lookup. Platform-hosted, pay per query with prepaid credit.
Repository
https://github.com/mcp-dir/sefaz_mt_nfce-mcp
Listing
From the official MCP registry (active).
Recent checks of SEFAZ MT: NFC-e
CheckedResultHandshake
1 hour agoHandshake completed48 ms
1 day agoHandshake completed79 ms
2 days agoHandshake completed63 ms
3 days agoFailed - the request timed out—
4 days agoHandshake completed79 ms
5 days agoHandshake completed111 ms
6 days agoHandshake completed57 ms
8 days agoHandshake completed253 ms
11 days agoHandshake completed59 ms
13 days agoHandshake completed370 ms
16 days agoHandshake completed114 ms
18 days agoHandshake completed72 ms
20 days agoHandshake completed121 ms
22 days agoHandshake completed51 ms
24 days agoFailed - the request timed out—
26 days agoHandshake completed123 ms
27 days agoHandshake completed92 ms
29 days agoHandshake completed56 ms

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