io.github.theluckystrike/credit-memo
MCPB · CREDIT-NOTE.MCPB · 2 COMPONENTS · SCANNED SEP 21
Issue a credit memo against an invoice or standalone, with per-line tax and totals.
Available components
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 Security23
- Malware scan not yet available for this package.Unverified
- Known CVEs were checked across the 96 of 96 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 10 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
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.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
mcpb · credit-note.mcpb
Download bundleEvery 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.
- 17 Sept 26 46
First indexed and scored.
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 Sept 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/credit-note.mcpb@0.22.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
credit_note_create Issue a credit note ~282
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | 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 | yes | 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 | yes | 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 | yes | Who the credit is for, e.g. Acme GmbH |
No output schema declared.
No examples provided.
credit_note_delete Delete a draft credit note ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The draft id, e.g. CN-DRAFT-2026-0001 |
No output schema declared.
No examples provided.
credit_note_finalize Finalize a credit note ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The draft id, e.g. CN-DRAFT-2026-0001 |
No output schema declared.
No examples provided.
credit_note_get Read one credit note in full ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The credit note number CN-2026-0001 or draft id CN-DRAFT-2026-0001 |
No output schema declared.
No examples provided.
credit_note_list List credit notes ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
credit_note_render Render a credit note as Markdown or printable HTML ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | markdown (default) or html, a self-contained printable page |
| id | string | yes | The credit note number CN-2026-0001 or draft id CN-DRAFT-2026-0001 |
No output schema declared.
No examples provided.
credit_note_summary Total credited by period, currency and reason ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
credit_note_update Revise a draft credit note ~194
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | – | – |
No output schema declared.
No examples provided.
license_activate Activate license ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from the checkout confirmation page |
No output schema declared.
No examples provided.
license_status License status ~54
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.