SEFAZ CE: NFE MCP Server

by mcp-dir Your server? Claim it

answering

SEFAZ CE: NFE is answering right now. Last checked 3 min ago. It exposes 7 tools. Last commit 19 Aug 2026.

SEFAZ CE: NFE, official-source lookup. Platform-hosted, pay per query with prepaid credit.

Uptime history 59 days of history · worst day 91%

59 days agonow

96.7%

Uptime 24h

89 of 92 checks

Tools

read from the server

1922 ms

Response time

average over 24h

Stars

last commit 19 Aug 2026

What changed 81

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 21 August 2026. No other catalogue keeps this.

11 Oct a tool changed version3 times that day

8 Oct a tool changed version

6 Oct a tool changed version3 times that day

5 Oct a tool changed version

3 Oct a tool changed version

2 Oct a tool changed version2 times that day

1 Oct a tool changed version

13 Sep a tool changed version

9 Sep a tool changed version

8 Sep a tool changed version

and 71 more, back to 21 August 2026

SEFAZ CE: NFE does not always answer

Over the last week it answered 98.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add sefaz_ce_nfe-mcp --transport http https://api.mcp.ai/p_sefaz_ce_nfe

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "sefaz_ce_nfe-mcp": {
      "url": "https://api.mcp.ai/p_sefaz_ce_nfe"
    }
  }
}

~/.codex/config.toml

[mcp_servers.sefaz_ce_nfe-mcp]
url = "https://api.mcp.ai/p_sefaz_ce_nfe"

.cursor/mcp.json

{
  "mcpServers": {
    "sefaz_ce_nfe-mcp": {
      "url": "https://api.mcp.ai/p_sefaz_ce_nfe"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "sefaz_ce_nfe-mcp": {
      "url": "https://api.mcp.ai/p_sefaz_ce_nfe"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

authenticate

authenticate

MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.

connect

connect

Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.

marketplace

marketplace

The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.

report

report_bug

Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

sefaz

sefaz_ce_nfe_consultar

SEFAZ CE: NFE, consulta em fonte oficial. Hospedado pela plataforma, sem credenciais da plataforma, pague por consulta com crédito pré-pago. Consulta informação de fontes e órgãos oficiais brasileiros (a mesma disponível ao cidadão), não é dado sigiloso. O cliente é o controlador dos dados e responde pela finalidade legítima (LGPD).

show

show_version

Show the current MCP platform and adapter versions.

toolkit

toolkit_info

Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

Endpoints

URL	Transport	State	Latency	Checked
https://api.mcp.ai/p_sefaz_ce_nfe	streamable-http	answering	722 ms	3 min ago

Alternatives to SEFAZ CE: NFE

same job, measured the same way

SEFAZ SC: NFE

by mcp-dir

SEFAZ SC: NFE, official-source lookup. Platform-hosted, pay per query with prepaid credit.

7 tools answering

SEFAZ SP: NFE

by mcp-dir

SEFAZ SP: NFE, official-source lookup. Platform-hosted, pay per query with prepaid credit.

7 tools answering

SEFAZ CE: NFC-e

by mcp-dir

SEFAZ CE: NFC-e, official-source lookup. Platform-hosted, pay per query with prepaid credit.

7 tools answering

SEFAZ: PR

by mcp-dir

SEFAZ: PR, official-source lookup. Platform-hosted, pay per query with prepaid credit.

7 tools answering

SEFAZ PE: NFC-e

by mcp-dir

SEFAZ PE: NFC-e, official-source lookup. Platform-hosted, pay per query with prepaid credit.

7 tools answering

SEFAZ PA: NFC-e

by mcp-dir

SEFAZ PA: NFC-e, official-source lookup. Platform-hosted, pay per query with prepaid credit.

7 tools answering

SEFAZ PR: NFC-e

by mcp-dir

SEFAZ PR: NFC-e, official-source lookup. Platform-hosted, pay per query with prepaid credit.

7 tools answering

SEFAZ SE: NFC-e

by mcp-dir

SEFAZ SE: NFC-e, official-source lookup. Platform-hosted, pay per query with prepaid credit.

7 tools answering

SEFAZ CE: NFE — questions

Answers built from our own checks of this server.

What can SEFAZ CE: NFE do?

It exposes 7 tools, read directly from the server on our last check. Among them: authenticate, connect, marketplace, report_bug, sefaz_ce_nfe_consultar, show_version and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is SEFAZ CE: NFE working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 92 checks got a reply (96.7%), average response time 1922 ms. The bar chart above shows every period we have measured.

How do I connect SEFAZ CE: NFE?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does SEFAZ CE: NFE need an API key?

No. SEFAZ CE: NFE completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is SEFAZ CE: NFE?

It answers our handshake in 1922 ms on average, which is faster than 1% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is SEFAZ CE: NFE open source?

Yes — it is published under the MIT licence and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.