billingengine-mcp

MCPcommunity
v0.1.1Timo KleemannMITUpdated 3d agonpmGitHub

MCP server for BillingEngine: create customers and invoices, look up invoices and record payments from Claude, Cursor and other MCP clients.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
377Downloads/wk
3d agoLast update
Needs 1 credential before it runs
  • BILLINGENGINE_API_KEYAPI keyrequired

    API key from Settings > API in BillingEngine (paid plans only)

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorTimo Kleemann
LicenseMIT
Version0.1.1
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface10 tools · none privileged
Security scan✓ Cleanv0.1.1 · todayHow well does this scan work?
EvalsNone
IndexedOct 6, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

10 tools · none privileged
Statically extracted from the published packagev0.1.1 · 5h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

find_customersLists customers, optionally filtered by a search text that matches company, names and email.

Lists customers, optionally filtered by a search text that matches company, names and email.

No input schema was published for this tool.

create_customerCreates a customer. Needs a company or a last name and a full address (line 1, postal code, city, country).

Creates a customer. Needs a company or a last name and a full address (line 1, postal code, city, country).

No input schema was published for this tool.

update_customerChanges the given fields of a customer; fields that are left out stay as they are.

Changes the given fields of a customer; fields that are left out stay as they are.

No input schema was published for this tool.

create_invoiceCreates a draft invoice for a customer. Number, language, texts and VAT treatment come from the account settings.

Creates a draft invoice for a customer. Number, language, texts and VAT treatment come from the account settings.

No input schema was published for this tool.

update_invoiceChanges a draft invoice. Passing items replaces all existing items, so send the complete list. Sent invoices cannot be changed.

Changes a draft invoice. Passing items replaces all existing items, so send the complete list. Sent invoices cannot be changed.

No input schema was published for this tool.

list_invoicesLists invoices, newest first. Status: draft, open (sent and unpaid), overdue (open and past due) or paid.

Lists invoices, newest first. Status: draft, open (sent and unpaid), overdue (open and past due) or paid.

No input schema was published for this tool.

get_invoiceReturns one invoice with its items, amounts and payment status.

Returns one invoice with its items, amounts and payment status.

No input schema was published for this tool.

download_invoiceSaves the PDF or the XML e-invoice of an invoice on this computer and returns the file path.

Saves the PDF or the XML e-invoice of an invoice on this computer and returns the file path.

No input schema was published for this tool.

record_paymentRecords a payment for one or more sent, open invoices of the same customer and tax rate. The amount is gross.

Records a payment for one or more sent, open invoices of the same customer and tax rate. The amount is gross.

No input schema was published for this tool.

list_paymentsLists recorded payments, newest first, optionally only those for one invoice.

Lists recorded payments, newest first, optionally only those for one invoice.

No input schema was published for this tool.

10 of 10 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for BillingEngine: create customers and invoices, look up invoices and record payments from Claude, Cursor and other MCP clients.

Keywords
mcpmodel-context-protocolinvoicinginvoicee-invoicebillingenginexrechnungzugferd
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-07 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in finance & trading