Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.mrfentmen/billbee-mcp

NPM · BILLBEE-MCP

MCP server for Billbee: orders, customers, ad MCP: real tools for real work.

Available components

+6 this week 68 Trust /100

Last scanned (19 hours ago)

Scores higher than 39% of npm servers

Category E-commerce

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1230 tokens (~42/item across 29 items; 29 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_order_message" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Nov 26 +6
    • Stability: unverified → 0.37 ▲ functional
  • 8 Nov 26 62

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/billbee-mcp@1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 29 exposed · ~1,230 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add_order_shipment ~61

Attach a shipment (carrier, tracking number) to an order.

NameTypeReqDescription
idintegeryesBillbee order id
shipmentobjectyesBillbee shipment object, e.g. {"ProviderId": 1, "TrackingCode": "..."}

No output schema declared.

No examples provided.

add_order_tags ~48

Set the tags attached to an order. This replaces the order's current tag list.

NameTypeReqDescription
idintegeryesBillbee order id
tagsarrayyesTag names to attach

No output schema declared.

No examples provided.

create_customer ~38

Create a customer in Billbee. The body is passed straight through as Billbee customer JSON.

NameTypeReqDescription
customerobjectyesBillbee customer object

No output schema declared.

No examples provided.

create_order ~48

Create an order in Billbee. The body is passed straight through as the Billbee order JSON.

NameTypeReqDescription
orderobjectyesBillbee order object (see the Billbee API docs for fields)

No output schema declared.

No examples provided.

create_shipment_with_label ~36

Create a shipment and buy its label in one call.

NameTypeReqDescription
shipmentobjectyesBillbee ship-with-label request object

No output schema declared.

No examples provided.

create_webhook ~52

Register a webhook. The body is passed through as Billbee webhook JSON.

NameTypeReqDescription
webhookobjectyesWebhook object, e.g. {"Type": 1, "TargetUrl": "https://..."}

No output schema declared.

No examples provided.

delete_webhook ~30

Delete a webhook by id. This cannot be undone.

NameTypeReqDescription
idintegeryesWebhook id

No output schema declared.

No examples provided.

find_order_by_ext_ref ~39

Find an order by the external order number used by the connected shop.

NameTypeReqDescription
extRefstringyesExternal order reference / order number

No output schema declared.

No examples provided.

get_customer ~27

Fetch one Billbee customer by id.

NameTypeReqDescription
idintegeryesBillbee customer id

No output schema declared.

No examples provided.

get_order ~30

Fetch a single Billbee order by its internal id.

NameTypeReqDescription
idintegeryesBillbee order id

No output schema declared.

No examples provided.

get_product ~29

Fetch one product by id, including its description.

NameTypeReqDescription
idintegeryesBillbee product id

No output schema declared.

No examples provided.

list_customer_addresses ~28

List every stored address of one customer.

NameTypeReqDescription
idintegeryesBillbee customer id

No output schema declared.

No examples provided.

list_customer_orders ~48

List the orders belonging to one customer.

NameTypeReqDescription
idintegeryesBillbee customer id
pageinteger–Page number
pageSizeinteger–Orders per page

No output schema declared.

No examples provided.

list_customers ~36

List Billbee customers with paging.

NameTypeReqDescription
pageinteger–Page number
pageSizeinteger–Customers per page

No output schema declared.

No examples provided.

list_invoices ~41

List invoices created in Billbee, optionally paged.

NameTypeReqDescription
pageinteger–Page number
pageSizeinteger–Invoices per page

No output schema declared.

No examples provided.

list_order_states ~21

List every order state id and name defined on the account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_orders ~124

List Billbee orders, newest first. Paging is 1-based; 50 per page is the API default.

NameTypeReqDescription
maxOrderDatestring–ISO date/time upper bound
minOrderDatestring–ISO date/time lower bound, e.g. 2026-01-01
orderStateIdinteger–Only orders in this state id
pageinteger–Page number, starting at 1
pageSizeinteger–Orders per page
shopIdinteger–Only orders from this shop id

No output schema declared.

No examples provided.

list_payment_types ~21

List every payment type id and name defined on the account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_product_stocks ~37

List current stock levels per product.

NameTypeReqDescription
pageinteger–Page number
pageSizeinteger–Rows per page

No output schema declared.

No examples provided.

list_products ~35

List Billbee products with paging.

NameTypeReqDescription
pageinteger–Page number
pageSizeinteger–Products per page

No output schema declared.

No examples provided.

list_shipping_carrier_enums ~25

List the shipping carrier enum values Billbee accepts in shipment objects.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_shipping_carriers ~19

List the shipping carriers configured on the account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_shipping_providers ~18

List the shipping providers available for labels.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_webhooks ~18

List the webhooks registered on the account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

patch_order ~57

Patch one or more fields of an existing Billbee order. Only the fields you pass are changed.

NameTypeReqDescription
idintegeryesBillbee order id
patchobjectyesFields to update, e.g. {"Comment": "..."}

No output schema declared.

No examples provided.

patch_product ~48

Patch fields of an existing product, such as title, price or stock settings.

NameTypeReqDescription
idintegeryesBillbee product id
patchobjectyesFields to update on the product

No output schema declared.

No examples provided.

send_order_message ~55

Send a message to the buyer of an order through Billbee.

NameTypeReqDescription
idintegeryesBillbee order id
messageobjectyesMessage object, e.g. {"Subject": "...", "Body": "..."}

No output schema declared.

No examples provided.

set_order_state ~100

Change the main state of an order (and optionally notify the buyer). Use list_order_states to find state ids.

NameTypeReqDescription
commentstring–Comment stored with the state change
idintegeryesBillbee order id
orderStateIdintegeryesTarget order state id
sendMailboolean–Send the buyer an email about the change
sendMessageboolean–Send the buyer an in-platform message

No output schema declared.

No examples provided.

update_product_stock ~61

Set the current stock level of a product.

NameTypeReqDescription
extraobject–Additional Billbee stock fields, e.g. {"Reason": "..."}
productIdintegeryesBillbee product id
stocknumberyesNew absolute stock level

No output schema declared.

No examples provided.

Install

How do I install the io.github.mrfentmen/billbee-mcp server?

io.github.mrfentmen/billbee-mcp runs locally as an npm package, launched with npx -y billbee-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · billbee-mcp

# add to Claude Code
claude mcp add mrfentmen-billbee-mcp -- npx -y billbee-mcp
Common questions

What is the io.github.mrfentmen/billbee-mcp server?

io.github.mrfentmen/billbee-mcp is listed in the public MCP registry as io.github.mrfentmen/billbee-mcp. MCP server for Billbee: orders, customers, ad MCP: real tools for real work. This page covers its npm package (billbee-mcp).

Is the io.github.mrfentmen/billbee-mcp server safe to use?

io.github.mrfentmen/billbee-mcp scores 68 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.mrfentmen/billbee-mcp server expose?

io.github.mrfentmen/billbee-mcp exposes 29 tools: list_orders, create_order, get_order, patch_order, set_order_state, and 24 more. Their descriptions and schemas cost roughly 1,230 tokens of context every time the server is loaded.

Is the io.github.mrfentmen/billbee-mcp server still maintained?

io.github.mrfentmen/billbee-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.mrfentmen/billbee-mcp server under?

io.github.mrfentmen/billbee-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.mrfentmen/billbee-mcp server?

VerifyMCP ran 16 checks on io.github.mrfentmen/billbee-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.