Remote MCP · Endpoint

SEFAZ PB: NFC-e MCP server

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

UpLast checked 1 hour ago

Server URL

https://api.mcp.ai/p_sefaz_pb_nfce

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/sefaz_pb_nfce-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
96 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
SEFAZ PB: NFC-e, official-source lookup. Platform-hosted, pay per query with prepaid credit.
Repository
https://github.com/mcp-dir/sefaz_pb_nfce-mcp
Listing
From the official MCP registry (active).
Recent checks of SEFAZ PB: NFC-e
CheckedResultHandshake
1 hour agoHandshake completed96 ms
2 days agoHandshake completed2.31 s
4 days agoHandshake completed39 ms
5 days agoHandshake completed269 ms
7 days agoHandshake completed43 ms
8 days agoHandshake completed223 ms
9 days agoHandshake completed64 ms
12 days agoHandshake completed38 ms
14 days agoHandshake completed150 ms
15 days agoHandshake completed537 ms
17 days agoHandshake completed70 ms
18 days agoHandshake completed58 ms
19 days agoHandshake completed55 ms
20 days agoHandshake completed220 ms
20 days agoHandshake completed81 ms
22 days agoHandshake completed573 ms
23 days agoHandshake completed1.43 s

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