Remote MCP · Endpoint

SEFAZ BA: NFC-e (Completa) MCP server

No. SEFAZ BA: NFC-e (Completa) answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://api.mcp.ai/p_sefaz_ba_nfce_completa

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/sefaz_ba_nfce_completa-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
162 ms
Tools exposed
7 tools
Uptime, last 30 days
88.9% from 18 checks
Described by its publisher as
SEFAZ BA: NFC-e (Completa), official-source lookup. Platform-hosted, pay per query with prepaid cred
Listing
From the official MCP registry (active).
Recent checks of SEFAZ BA: NFC-e (Completa)
CheckedResultHandshake
7 hours agoHandshake completed162 ms
1 day agoHandshake completed91 ms
3 days agoFailed - the request timed out—
3 days agoHandshake completed1.04 s
4 days agoHandshake completed69 ms
6 days agoHandshake completed154 ms
8 days agoHandshake completed475 ms
10 days agoHandshake completed52 ms
13 days agoHandshake completed1.41 s
15 days agoHandshake completed69 ms
17 days agoHandshake completed63 ms
19 days agoHandshake completed340 ms
21 days agoHandshake completed42 ms
23 days agoFailed - the request timed out—
25 days agoHandshake completed81 ms
27 days agoHandshake completed71 ms
28 days agoHandshake completed116 ms
29 days agoHandshake completed41 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.

Listing data comes from the official MCP registry. Glide is not affiliated with SEFAZ BA: NFC-e (Completa) and makes no claim about it beyond what these checks measured.