Fiscal vs Tokentrust

A side-by-side look at the Fiscal and Tokentrust MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Fiscal logoFiscalFinance & Fintech · Remote HTTP/SSEBrazilian fiscal MCP server - issue NF-e, NFC-e, NFS-e, CT-e, MDF-e and DC-e via SEFAZ.49FairAuth: no auth requiredTokentrust logoTokentrustConversational AI · Local subprocess (stdio)Verifies token/cost savings claimed by AI context-reduction proxies via MCP tools.44FairAuth: not declared

Verdict: choose Fiscal for finance & fintech work over a hosted endpoint; choose Tokentrust for conversational ai as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Fiscal logoChoose Fiscal when

  • You need dedicated capabilities in the Finance & Fintech domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: No auth required.
Explore Fiscal

Tokentrust logoChoose Tokentrust when

  • You need dedicated capabilities in the Conversational AI domain.
  • You prefer a local stdio subprocess transport.
Explore Tokentrust

Feature & specification comparison

Rows where the two servers differ are marked.

SpecFiscal logoFiscalTokentrust logoTokentrust
CategoryFinance & FintechConversational AI
Quality signal49/100 · Fair44/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNo auth requiredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars00
Directory activity 0 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Fiscal tools

No tool names declared yet. Check the project README from the listing page.

Tokentrust tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Fiscal

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "fiscal": {
      "command": "npx",
      "args": [
        "-y",
        "fiscal"
      ]
    }
  }
}

Tokentrust

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "tokentrust": {
      "command": "npx",
      "args": [
        "-y",
        "tokentrust-cli"
      ]
    }
  }
}

Frequently asked questions

Fiscal is categorized under Finance & Fintech and uses a remote HTTP/SSE transport. Tokentrust belongs to Conversational AI and uses a local stdio subprocess. Pick Fiscal for finance & fintech work and Tokentrust for conversational ai.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Fiscal has no declared pricing — check the project's own site. Auth: no auth required. Tokentrust has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add fiscal and tokentrust as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Fiscal has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Tokentrust has 44/100 (Fair) with 4 views, 0 installs and 0 GitHub stars.