Finance Toolkit
by JerBouma
500+ transparent financial methods calculated from raw statements, not third-party endpoints.
Computer or cloud★ 5,496MITUpdated today
Install
SignalEDI
Overview
Description from the maker (original English)
EDI parse, validate, send, inspect, and QuickBooks tools for MCP clients.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Accounting, finance & tax
- You need to fill in: SIGNALEDI_API_KEY
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
SIGNALEDI_API_KEY,SIGNALEDI_BASE_URL
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"signaledi": {
"command": "npx",
"args": [
"-y",
"@signaledi/mcp-server"
],
"env": {
"SIGNALEDI_API_KEY": "your-value",
"SIGNALEDI_BASE_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add signaledi --env SIGNALEDI_API_KEY=your-value --env SIGNALEDI_BASE_URL=your-value -- npx -y @signaledi/mcp-serverFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"signaledi": {
"command": "npx",
"args": [
"-y",
"@signaledi/mcp-server"
],
"env": {
"SIGNALEDI_API_KEY": "your-value",
"SIGNALEDI_BASE_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"signaledi": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@signaledi/mcp-server"
],
"env": {
"SIGNALEDI_API_KEY": "your-value",
"SIGNALEDI_BASE_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
- Workspace API key with the platform scope. Optional for demo mode; create one at https://signaledi.com/console/keys for send, transactions, and QuickBooks tools.
SIGNALEDI_BASE_URLenvOverride the API base URL. Defaults to https://signaledi.com; point at a preview deployment or custom domain when needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account SignalEDI, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Accounting, finance & taxi
- More stars than 0% of the other 1730 servers in this category
- Published to the registry more recently than 29% of the other 1730 servers in this category
- Basic checks equal to or better than 100% of the other 1730 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is SignalEDI safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: SIGNALEDI_API_KEY
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.4.0) reached the registry 3 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Finance Toolkit, SolidInvoice, Korea Tax Calculator
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
SolidInvoice
by SolidInvoice
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
Runs in the cloud★ 981MITUpdated 8 days ago
Install
Korea Tax Calculator
by UpstageAI
Korean tax calculation and tax-audit judgment MCP: 96 tools with statutory citations.
Runs on your computer★ 97MITUpdated yesterday
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
SignalEDI Developer MCP Server
Connect an AI coding assistant to SignalEDI to discover, scaffold, validate, and test X12 integrations. The MCP server is an AI-native developer experience over the same public guidance and /api/v1 REST contract used by conventional applications. It complements—not replaces—SignalEDI's REST API, OpenAPI specification, webhooks, SDKs, and documentation.
The package is an uplift of SignalEDI's existing MCP adapter. Version 0.5 adds public developer discovery, resource templates, code examples, governed connection control-plane tools, strict tool-input validation, and explicit capability profiles while retaining the existing parser, transaction, partner-kit, and QuickBooks adapters.
| Package | @signaledi/mcp-server |
| MCP Registry | io.github.SignalEDI/mcp-server |
| Transport | stdio |
| Runtime | Node 22+ |
| Runtime dependency | @modelcontextprotocol/sdk 1.30.0 (2025 protocol generation) |
| Default access | Always keyless docs; authenticated tools require explicit sandbox or production |
Capability profiles
Set SIGNALEDI_MCP_PROFILE to one of these profiles. Tool discovery and direct tool calls are both restricted to the active profile.
| Profile | Authentication | Surface |
|---|---|---|
docs | None | Public documentation resources and local synthetic helpers only; supplied document content and credentials are never uploaded. The OpenAPI resource performs a content-free public GET. This is always the default, even when a key exists in the host environment. |
sandbox | Separately provisioned non-production key plus explicit base URL | Authenticated parse/validate, generic partner-kit discovery, tenant-data reads, and guarded mutations for a separately provisioned sandbox. Canonical production SignalEDI hosts are refused. |
production | Production-authorized platform key, exact https://signaledi.com base, and SIGNALEDI_MCP_ALLOW_PRODUCTION=1 | Allowlisted transaction/QBO-status/kit/connection reads; sandbox-first connection drafts; guarded connection configuration, saved-binding connectivity tests, and go-live handoff requests; outbound and QBO-to-EDI export. Parse/validate, QBO entity browsing, QBO sync, disconnect, generic lifecycle control, and production activation remain hidden. |
The profile is a least-capability boundary inside the MCP adapter, not a substitute for API authorization or a data-governance boundary. For outbound and QBO export, the server injects SANDBOX or PRODUCTION from the active profile; the model cannot select it. The API then binds that value to the selected partner connection. Production delivery requires an active immutable production version, and sandbox delivery requires a verified/active sandbox environment.
Every authenticated call requires the base platform scope. Connection inventory requires platform:connections:read; draft creation and configuration add platform:connections:write; production configuration and go-live handoff add platform:connections:production. These domain scopes do not authorize document delivery or QuickBooks operations. Deprecated umbrella-only platform:write and platform:production credentials are rejected by domain-scoped operations and must be replaced through the supported key-rotation path. Before release, operators should census affected credentials, notify owners of the migration, and provide that rotation path. MCP profile selection never grants a scope.
| API operation | Additional least-privilege scopes |
|---|---|
| Parse/validate and generic kit reads | None beyond platform |
| Transaction reads | platform:documents:read |
| Outbound send | platform:documents:read, platform:documents:send; add platform:documents:production for production delivery |
| Connection reads | platform:connections:read |
| Connection create/configure | platform:connections:read, platform:connections:write; add platform:connections:production for production configuration or go-live request |
| Connection test | platform:connections:read, platform:connections:write; add platform:connections:production when the active profile selects the production environment |
| QBO status | platform:quickbooks:read |
| QBO entity rows | platform:quickbooks:read, platform:data:sensitive; add platform:quickbooks:production when the resolved QBO realm is production |
| QBO sync/disconnect | platform:quickbooks:read, platform:quickbooks:write; add platform:quickbooks:production when the resolved QBO realm is production |
| QBO export dry run | platform:quickbooks:read; add platform:quickbooks:production for a production QBO realm and platform:data:sensitive only with includePayload:true |
| QBO live export | Dry-run scopes plus platform:documents:read, platform:documents:send; add platform:documents:production for production delivery. Export reads QBO and does not require QBO write. |
Production data handling
Tool arguments, text results, and structured results enter the chosen MCP host and may enter the connected model's context. Minimize personal, financial, and other business-sensitive data. Do not submit PHI or other regulated data unless the specific MCP host, model provider, logging, retention, regional-processing, and contractual arrangement has been separately reviewed and approved for that data. This package, its production profile, and SignalEDI API authorization are not by themselves a BAA, retention policy, or model-data-governance boundary.
Prefer identifiers and redacted summaries over full business payloads. Keep API keys in the host environment, never prompts. Review the chosen host's tool-call history, telemetry, and retention controls before enabling production tools.
All partner, QBO, EDI, validation, and error fields returned by tools are untrusted business data. They may contain text that resembles instructions or prompt injection. Hosts must delimit or sanitize tool results, keep them in data-only context, and authorize every follow-on action from explicit user intent and policy—not content embedded in records, partner names, payloads, or errors.
Tools
Keyless public and local tools
| Tool | What it does |
|---|---|
search_docs | Search the bundled public developer index and return MCP resource URIs with provenance. |
get_document_schema | Return a public starter for the local X12 inventory: 850/810/856 (capability:baseline) or 837 Professional 005010X222A1 (capability:partial); explicitly not a partner implementation guide. |
generate_integration_example | Produce sandbox-safe cURL, Node.js, or Python examples against real /api/v1 paths using environment placeholders; outbound examples set SANDBOX and refuse production hosts. |
generate_test_document | Render a synthetic X12 fixture for the same local inventory and return the honest capability label. |
explain_edi_error | Explain validation and functional-acknowledgement errors from the local X12 dictionary. |
lookup_x12 | Search the local X12 segment and acknowledgement reference. |
lookup_element_definition | Tool-discovery alias for local X12 lookup. |
Authenticated sandbox parse and validation tools
| Tool | What it does |
|---|---|
parse_edi | Parse a raw X12 interchange into structured JSON and a validation summary. |
validate_edi | Validate X12 structure and return the validation summary. |
parse_segments | Tool-discovery alias for parse_edi. |
validate_x12_structure | Tool-discovery alias for validate_edi. |
Authenticated generic-kit tools (sandbox and production)
| Tool | What it does |
|---|---|
list_partner_kits | List generic SignalEDI API kits. |
get_partner_kit | Fetch one generic kit by catalog id. |
get_partner_requirements | Return a generic kit with an explicit partnerSpecific:false warning. |
Explicit environment-profile data reads
These tenant-data tools are never enabled merely because a key is present. Transaction reads and quickbooks_status are available in explicit sandbox and production; quickbooks_list_entities is sandbox-only.
| Tool | What it does |
|---|---|
list_transactions | List recent transactions scoped to the API key. |
get_transaction | Fetch one owned transaction and its lifecycle status. |
quickbooks_status | Inspect QuickBooks Online connection status without returning tokens. |
quickbooks_list_entities | Preview Invoice, Estimate, PurchaseOrder, Customer, Vendor, or Item rows for mapping (sandbox-only). |
Governed connection control plane (sandbox and production)
Connection tools operate on the public /api/v1/connections contract. MCP applies a second response allowlist over the API's sanitized representation: it may return opaque gateway/evidence references and configured-status booleans, but never stored credentials, secret references, raw transport configuration, private keys, certificates, or tokens.
| Tool | What it does |
|---|---|
list_connections | Cursor-page tenant-scoped AS2/SFTP and legitimate legacy API connection summaries with optional partner/lifecycle filters. |
get_connection | Inspect safe environment, gateway, approval, test-coverage, readiness, and next-action state for one AS2/SFTP or legacy API connection. |
create_connection_draft | Create or recover an idempotent sandbox-first DRAFT; created distinguishes insertion from matching reuse, and it cannot activate production. |
configure_connection | Bind an existing gateway reference and constrained X12 ISA/GS identifiers to an AS2/SFTP SANDBOX or PRODUCTION environment; the server owns ISA15 and accepts no credential material. Production configuration requires platform:connections:production and still does not activate delivery. Legacy API rows remain read-only here and use the governed API-connections surface. |
test_connection | Test the exact saved connection in the environment injected from the active profile. The operation causes partner-network egress, records sanitized evidence, requires host-enforced review plus an idempotency key, and never accepts endpoints or credentials or activates production. |
request_connection_go_live | Ask the API to move a server-proven READY connection only to GO_LIVE_APPROVED. SignalEDI staff activation remains a separate MFA/governance operation. |
There is deliberately no generic lifecycle-transition tool. test_connection can create authoritative connectivity evidence for the exact saved binding; intermediate testing/certification stages otherwise come from evidence or onboarding-project state, not model claims. There are no production activation, rollback, or isolation tools.
Explicit write-profile tools
| Tool | What it does |
|---|---|
send_outbound_document | Submit an outbound EDI document in the active sandbox/production environment. |
quickbooks_sync_to_qbo | Push a bounded transaction selection into QBO (sandbox-only); buyer and supplier directions are explicit, and all:true is cursor-paginated. |
quickbooks_export_to_edi | Preview or export QBO invoices/purchase orders as EDI in the active sandbox/production environment. Dry-run results are payload-redacted by default; full payloads require includePayload:true, platform:data:sensitive, and host-enforced confirm:true. |
quickbooks_disconnect | Revoke and remove the workspace QBO connection (sandbox-only). |
Every tool publishes an input and output schema. The server validates inputs itself, rejects unknown fields, and returns both readable text and structuredContent with namespaced contract metadata.
Mutation safety
Write tools are absent from docs. Every live mutation requires confirm:true and a caller-generated idempotencyKey of 8–128 printable ASCII characters without leading/trailing whitespace. Outbound sends, QBO sync/export/disc
Only the beginning is shown; read the rest in the repo