io.github.theluckystrike/credit-memo
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20
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 against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 11 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
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.
remote · mcp.zovo.one
claude mcp add --transport http theluckystrike-credit-memo 'https://mcp.zovo.one/mcp/credit-note'
{
"mcpServers": {
"theluckystrike-credit-memo": {
"url": "https://mcp.zovo.one/mcp/credit-note"
}
}
} {
"servers": {
"theluckystrike-credit-memo": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/credit-note"
}
}
} [mcp_servers.theluckystrike-credit-memo] url = "https://mcp.zovo.one/mcp/credit-note"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-credit-memo": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/credit-note",
"enabled": true
}
}
} openclaw mcp add theluckystrike-credit-memo --url 'https://mcp.zovo.one/mcp/credit-note' --transport streamable-http
mcp_servers:
theluckystrike-credit-memo:
url: "https://mcp.zovo.one/mcp/credit-note" {
"McpServers": {
"theluckystrike-credit-memo": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/credit-note"
}
}
} assistant mcp add theluckystrike-credit-memo -t streamable-http -u 'https://mcp.zovo.one/mcp/credit-note'
{
"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.
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.
- 20 Sept 26 +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.
- 18 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Sept 26 77
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 20 Sept 2026 · Probed https://mcp.zovo.one/mcp/credit-note
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ef74739bd6e575bb13db69661e215324 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token"
Bearer realm="mcp.zovo.one", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/credit-note | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/credit-note | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/credit-note |
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 ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
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.
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 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.