# io.github.theluckystrike/credit-memo (remote · mcp.zovo.one)

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

- Trust score: 79/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.zovo.one`: 79/100 (this document), [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, [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

- Endpoint: `https://mcp.zovo.one/mcp/credit-note`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-20.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1285 tokens (~116/item across 11 items; 10 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 11 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.theluckystrike/credit-memo MCP server?

io.github.theluckystrike/credit-memo is a hosted endpoint at https://mcp.zovo.one/mcp/credit-note, so there is nothing to install locally. 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 --transport http theluckystrike-credit-memo 'https://mcp.zovo.one/mcp/credit-note'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-credit-memo": {
      "url": "https://mcp.zovo.one/mcp/credit-note"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-credit-memo": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/credit-note"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-credit-memo]
url = "https://mcp.zovo.one/mcp/credit-note"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-credit-memo": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/credit-note",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-credit-memo --url 'https://mcp.zovo.one/mcp/credit-note' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-credit-memo:
    url: "https://mcp.zovo.one/mcp/credit-note"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-credit-memo": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/credit-note"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-credit-memo -t streamable-http -u 'https://mcp.zovo.one/mcp/credit-note'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-credit-memo": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/credit-note"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-20 (score 79, +1)

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

### 2026-09-18 (score 78, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-17 (score 77)

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` (~55 tokens)

License status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

### `license_activate` (~76 tokens)

Activate license

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-credit-memo/mcp-credit-note#diagnostics

## Score history

- 2026-09-20: 79
- 2026-09-19: 78
- 2026-09-18: 78
- 2026-09-17: 77

## 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 hosted endpoint (https://mcp.zovo.one/mcp/credit-note).

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

io.github.theluckystrike/credit-memo scores 79 out of 100 on VerifyMCP. 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,234 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/credit-memo MCP server require authentication?

Yes. io.github.theluckystrike/credit-memo asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.github.theluckystrike/credit-memo MCP server still maintained?

io.github.theluckystrike/credit-memo is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/credit-note
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/credit-note
- 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/mcp-credit-note.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-credit-memo/mcp-credit-note.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-credit-memo/mcp-credit-note