# io.github.theluckystrike/credit-memo (mcpb · credit-note.mcpb)

Issue a credit memo against an invoice or standalone, with per-line tax and totals.

- Trust score: 46/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `mcp.zovo.one`: 81/100, [markdown](https://verifymcp.io/servers/theluckystrike-credit-memo/mcp-credit-note.md), [page](https://verifymcp.io/servers/theluckystrike-credit-memo/mcp-credit-note)
- mcpb · `credit-note.mcpb`: 46/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-credit-memo/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-credit-not.md), [page](https://verifymcp.io/servers/theluckystrike-credit-memo/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-credit-not)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/credit-note.mcpb`
- Version: `0.22.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-09-21.

- **Supply Chain Security**: 23/100
  - Malware scan not yet available for this package.
  - Known CVEs were checked across the 96 of 96 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1228 tokens (~122/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 88% 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; "credit_note_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 10 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

- Download bundle: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/credit-note.mcpb`

## 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-09-17 (score 46)

First indexed and scored.

## MCP tools (10)

### `credit_note_create` (~282 tokens)

Issue a credit note

Issue a credit note against an invoice, or standalone: the recipient, the reason (returned goods, overcharge, discount correction, service issue, other), line items with quantity, unit price and tax rate, and the currency. Returns a draft you can still revise; credit_note_finalize burns the final CN number.

Input parameters:

- `currency` (string, required): ISO code the credit is in
- `duplicate_ok` (boolean): Create it even though an identical draft or note exists, for a genuinely repeated credit. Default false
- `invoice_ref` (string): The invoice this credits, e.g. INV-2026-0042. Omit for a standalone credit
- `issue_date` (string): The date the credit is issued, YYYY-MM-DD. Default today; a future date is refused
- `lines` (array, required): What is being credited, line by line
- `notes` (string): Text printed at the foot of the document, e.g. how the credit will be settled
- `reason` (string, required): Why the credit is issued: returned_goods, overcharge, discount_correction, service_issue or other
- `reason_detail` (string): One line of specifics, e.g. Client was billed 10 seats, used 7
- `recipient` (string, required): Who the credit is for, e.g. Acme GmbH

### `credit_note_update` (~194 tokens)

Revise a draft credit note

Change a draft credit note while it is still a draft: recipient, reason, lines, currency, invoice reference, issue date or notes. Pass only what changes; new lines replace all old ones. A finalized note is immutable and is refused by name.

Input parameters:

- `currency` (string): ISO code. Changing it reprices nothing: the stored minor units carry over, so only change it to fix a wrong currency
- `id` (string, required): The draft id, e.g. CN-DRAFT-2026-0001
- `invoice_ref`: New invoice reference, or null to detach the note from its invoice
- `issue_date` (string)
- `lines` (array): The full new line set, replacing every existing line
- `notes`: New notes text, or null to remove the notes
- `reason` (string)
- `reason_detail`
- `recipient` (string)

### `credit_note_finalize` (~90 tokens)

Finalize a credit note

Finalize a draft: burn the final CN-YYYY-NNNN number and freeze the note. From here it cannot be edited or deleted, only rendered and listed, because it is now the document the client sees. Free tier: 10 finalized credit notes; Pro removes the limit.

Input parameters:

- `id` (string, required): The draft id, e.g. CN-DRAFT-2026-0001

### `credit_note_list` (~156 tokens)

List credit notes

List credit notes: number or draft id, recipient, reason, status, issue date and total. Filter by recipient (a part of the name is enough), by reason, by status draft or final, and by issue-date period with from and to.

Input parameters:

- `from` (string): First issue date to include, YYYY-MM-DD
- `limit` (integer): Maximum notes listed, default and ceiling 2000
- `reason` (string): Only notes with this reason
- `recipient` (string): Match the recipient, case-insensitive, a part of the name is enough
- `status` (string): Only drafts or only finalized notes
- `to` (string): Last issue date to include, YYYY-MM-DD

### `credit_note_get` (~90 tokens)

Read one credit note in full

Return one credit note by its CN number or draft id: every line with quantity, unit price and tax, the totals per tax rate, the reason, the invoice it credits, and the notes. Reads only; use credit_note_list for the ids.

Input parameters:

- `id` (string, required): The credit note number CN-2026-0001 or draft id CN-DRAFT-2026-0001

### `credit_note_delete` (~74 tokens)

Delete a draft credit note

Delete a draft credit note entered wrongly, by its draft id. A finalized note is refused by name: it is a document the client may have seen, and deleting it would leave their copy pointing at nothing.

Input parameters:

- `id` (string, required): The draft id, e.g. CN-DRAFT-2026-0001

### `credit_note_render` (~121 tokens)

Render a credit note as Markdown or printable HTML

Turn a credit note into the document: Markdown to paste into an email or ticket, or a self-contained printable HTML page with every style inline. Drafts render with a DRAFT banner so a half-finished credit cannot be sent by mistake. Writes nothing. Free; the free tier stamps a one-line footer.

Input parameters:

- `format` (string): markdown (default) or html, a self-contained printable page
- `id` (string, required): The credit note number CN-2026-0001 or draft id CN-DRAFT-2026-0001

### `credit_note_summary` (~96 tokens)

Total credited by period, currency and reason

How much you have credited: totals per currency over finalized credit notes, broken down by reason and by month, in an optional issue-date period. Drafts count for nothing until they are finalized. Currencies are never added together.

Input parameters:

- `from` (string): First issue date to include, YYYY-MM-DD. Default: the beginning
- `to` (string): Last issue date to include, YYYY-MM-DD. Default: today

### `license_status` (~54 tokens)

License status

Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.

### `license_activate` (~71 tokens)

Activate license

Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.

Input parameters:

- `key` (string, required): License key from the checkout confirmation page

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/theluckystrike-credit-memo/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-credit-not#diagnostics

## Score history

- 2026-09-21: 46
- 2026-09-20: 46
- 2026-09-19: 46
- 2026-09-18: 46
- 2026-09-17: 46

## Common questions

### What is the io.github.theluckystrike/credit-memo MCP server?

io.github.theluckystrike/credit-memo is an MCP server listed in the public MCP registry as io.github.theluckystrike/credit-memo. Issue a credit memo against an invoice or standalone, with per-line tax and totals. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/credit-note.mcpb).

### Is the io.github.theluckystrike/credit-memo MCP server safe to use?

io.github.theluckystrike/credit-memo scores 46 out of 100 on VerifyMCP. 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.theluckystrike/credit-memo MCP server expose?

io.github.theluckystrike/credit-memo exposes 10 tools: credit_note_create, credit_note_update, credit_note_finalize, credit_note_list, credit_note_get, and 5 more. Their descriptions and schemas cost roughly 1,228 tokens of context every time the server is loaded.

### What licence is the io.github.theluckystrike/credit-memo MCP server under?

io.github.theluckystrike/credit-memo 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

- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/credit-note
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-credit-memo/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-credit-not.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-credit-memo/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-credit-not.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-credit-memo/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-credit-not