FOX NF-e

br.com.foxnfePublished by foxnfe.com.brOfficial publisherv1.0.0Updated Oct 25, 2026

Ferramentas MCP para NF-e, NFS-e, documentos, certificados e tributos brasileiros.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP server from FOX NF-e giving assistants tools for Brazilian NF-e and NFS-e invoices, documents, certificates and taxes.

What you can do
The manifest lists no individual tools, so capabilities come from the provider's description: tools for Brazilian electronic invoices (NF-e) and service invoices (NFS-e). It also covers documents, digital certificates and Brazilian tax matters. No further detail on specific operations is available.
When to use it
Consider it when an assistant needs to work with Brazilian electronic invoicing, fiscal documents, digital certificates or tax data, and the provider's own service is already part of your workflow.
Requirements
A remote streamable HTTP endpoint at the provider's site. Authentication is required: a bearer token in the Authorization header and a tenant identifier in the X-Tenant-ID header. No environment variables or local packages are declared.
Before you install
You must supply a bearer token and a tenant identifier, so treat both as secrets. The description mentions invoices, certificates and tax data, which are sensitive; the exact read or write behavior of the tools is not documented here, so confirm it with the provider before use.

Installation

In SourceWeft

  1. Open FOX NF-e in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/br.com.foxnfe%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "fox-nf-e": {
      "type": "http",
      "url": "https://www.foxnfe.com.br/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 23, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.