Remote MCP · Endpoint

DF-e MCP server

No. DF-e answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.mcp.ai/p_dfe

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/dfe-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
60 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Brazilian SEFAZ e-invoices (NF-e, CT-e) issued against your company. A1 cert, DANFE PDF.
Listing
From the official MCP registry (active).
Recent checks of DF-e
CheckedResultHandshake
1 hour agoHandshake completed60 ms
2 days agoHandshake completed104 ms
4 days agoHandshake completed37 ms
5 days agoHandshake completed33 ms
7 days agoHandshake completed204 ms
8 days agoHandshake completed125 ms
10 days agoHandshake completed1.35 s
12 days agoHandshake completed62 ms
14 days agoHandshake completed65 ms
15 days agoHandshake completed72 ms
17 days agoHandshake completed54 ms
18 days agoHandshake completed104 ms
19 days agoHandshake completed737 ms
20 days agoHandshake completed322 ms
20 days agoHandshake completed141 ms
21 days agoHandshake completed293 ms
23 days agoHandshake completed30 ms

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.

Listing data comes from the official MCP registry. Glide is not affiliated with DF-e and makes no claim about it beyond what these checks measured.