# io.github.mrfentmen/invoice-mcp (npm · invoice-mcp)

Generate and send invoices across carriers (UPS, USPS, FedEx, DHL).

- Trust score: 67/100 (medium)
- Change this week: −2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- npm · `invoice-mcp`: 67/100 (this document), [markdown](https://verifymcp.io/servers/mrfentmen-invoice-mcp/invoice-mcp.md), [page](https://verifymcp.io/servers/mrfentmen-invoice-mcp/invoice-mcp)

## Channel facts

- Registry: `npm`
- Package: `invoice-mcp`
- Version: `1.0.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-24.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 13/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Maintenance check failed: the publisher has marked this version as deprecated on the registry, telling users to stop installing it.
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 270 tokens (~38/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_invoice" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

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

### Claude

```bash
claude mcp add mrfentmen-invoice-mcp -- npx -y invoice-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "mrfentmen-invoice-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "invoice-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mrfentmen-invoice-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "invoice-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mrfentmen-invoice-mcp -- npx -y invoice-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mrfentmen-invoice-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "invoice-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mrfentmen-invoice-mcp --command npx --arg -y --arg invoice-mcp
```

### Hermes

```yaml
mcp_servers:
  mrfentmen-invoice-mcp:
    command: "npx"
    args: ["-y", "invoice-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "mrfentmen-invoice-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "invoice-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mrfentmen-invoice-mcp -t stdio -c npx -a -y invoice-mcp
```

### Other

```json
{
  "mcpServers": {
    "mrfentmen-invoice-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "invoice-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-24 (score 67, −5)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: pass → fail

### 2026-10-23 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-18 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 68, +6)

- [functional improvement] Stability: unverified → 0.43

### 2026-10-02 (score 62, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-01 (score 47)

First indexed and scored.

## MCP tools (7)

### `generate_invoice` (~33 tokens)

Generate an HTML invoice from invoice data.

Input parameters:

- `data` (string, required): JSON object with from, to, items, currency

### `convert_to_pdf` (~39 tokens)

Convert HTML invoice to PDF.

Input parameters:

- `htmlPath` (string, required): Path to HTML invoice file
- `outputPath` (string): Output PDF path

### `send_invoice` (~50 tokens)

Send invoice via carrier API.

Input parameters:

- `carrier` (string, required): Carrier to send via
- `pdfPath` (string, required): Path to PDF invoice
- `trackNumber` (string): Tracking number for existing shipment

### `validate_address` (~35 tokens)

Validate address for a specific carrier.

Input parameters:

- `address` (string, required): Address to validate
- `carrier` (string, required): Carrier for validation

### `create_label` (~66 tokens)

Create shipping label for an invoice.

Input parameters:

- `carrier` (string, required): Carrier
- `from` (string, required): Sender address
- `service` (string, required): Service level (e.g., ground, express)
- `to` (string, required): Recipient address
- `weight` (number, required): Package weight

### `track_shipment` (~34 tokens)

Track a shipment with carrier API.

Input parameters:

- `carrier` (string, required): Carrier
- `trackNumber` (string, required): Tracking number

### `list_carriers` (~13 tokens)

List supported carriers.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/mrfentmen-invoice-mcp/invoice-mcp#diagnostics

## Score history

- 2026-10-24: 67
- 2026-10-23: 72
- 2026-10-22: 71
- 2026-10-21: 71
- 2026-10-20: 70
- 2026-10-19: 70
- 2026-10-18: 70
- 2026-10-17: 69
- 2026-10-16: 69
- 2026-10-15: 68
- 2026-10-14: 68
- 2026-10-13: 62
- 2026-10-12: 62
- 2026-10-11: 62
- 2026-10-09: 62
- 2026-10-05: 62
- 2026-10-04: 62
- 2026-10-03: 62
- 2026-10-02: 62
- 2026-10-01: 47

## Common questions

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

io.github.mrfentmen/invoice-mcp is listed in the public MCP registry as io.github.mrfentmen/invoice-mcp. Generate and send invoices across carriers (UPS, USPS, FedEx, DHL). This page covers its npm package (invoice-mcp).

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

io.github.mrfentmen/invoice-mcp scores 67 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 24 October 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/invoice-mcp server expose?

io.github.mrfentmen/invoice-mcp exposes 7 tools: generate_invoice, convert_to_pdf, send_invoice, validate_address, create_label, and 2 more. Their descriptions and schemas cost roughly 270 tokens of context every time the server is loaded.

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

io.github.mrfentmen/invoice-mcp is still listed as active in the MCP registry. We last reached this channel on 24 October 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/invoice-mcp server under?

io.github.mrfentmen/invoice-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.

## Links

- npm package: https://www.npmjs.com/package/invoice-mcp
- Socket report: https://socket.dev/npm/package/invoice-mcp
- Changelog RSS feed: https://verifymcp.io/servers/mrfentmen-invoice-mcp/invoice-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mrfentmen-invoice-mcp/invoice-mcp.json
- HTML version of this page: https://verifymcp.io/servers/mrfentmen-invoice-mcp/invoice-mcp