Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.theluckystrike/credit-note

REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS

Credit notes against an invoice or standalone: drafts, finalization, rendering, totals.

−13 this week 81 Trust /100

Last scanned (14 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Recent critical change

Authorization (17 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability83
  • 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 1428 tokens (~129/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 Management94
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 0 breaking changes, 1 auth/transport breaks, 0 additions. See how to fix → Fail
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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 12 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 17 Nov 26 −13
    • Authorization: pass → fail ▼ critical
    • Stability: pass → fail ▼ security
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 2 Nov 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
Diagnostics

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 Nov 2026 · Probed https://mcp.zovo.one/mcp/credit-note-ics

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 31 Oct 2026 29 Jan 2027 ECDSA 256 ECDSA-SHA256 39e1adfa4eb6500e0e3d48868766e3e9
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. DS published 64939 8 Verified
zovo.one. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15552000; includeSubDomains; preload
x-content-type-options nosniff

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-ics Verified 200
http (plaintext) http://mcp.zovo.one/mcp/credit-note-ics HTTPS enforced 301 https://mcp.zovo.one/mcp/credit-note-ics
MCP tools · 10 exposed · ~1,234 tokens

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 →

Tool Tokens
credit_note_create ~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.

NameTypeReqDescription
currencystringyesISO code the credit is in
duplicate_okboolean–Create it even though an identical draft or note exists, for a genuinely repeated credit. Default false
invoice_refstring–The invoice this credits, e.g. INV-2026-0042. Omit for a standalone credit
issue_datestring–The date the credit is issued, YYYY-MM-DD. Default today; a future date is refused
linesarrayyesWhat is being credited, line by line
notesstring–Text printed at the foot of the document, e.g. how the credit will be settled
reasonstringyesWhy the credit is issued: returned_goods, overcharge, discount_correction, service_issue or other
reason_detailstring–One line of specifics, e.g. Client was billed 10 seats, used 7
recipientstringyesWho the credit is for, e.g. Acme GmbH

No output schema declared.

No examples provided.

credit_note_delete ~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.

NameTypeReqDescription
idstringyesThe draft id, e.g. CN-DRAFT-2026-0001

No output schema declared.

No examples provided.

credit_note_finalize ~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.

NameTypeReqDescription
idstringyesThe draft id, e.g. CN-DRAFT-2026-0001

No output schema declared.

No examples provided.

credit_note_get ~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.

NameTypeReqDescription
idstringyesThe credit note number CN-2026-0001 or draft id CN-DRAFT-2026-0001

No output schema declared.

No examples provided.

credit_note_list ~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.

NameTypeReqDescription
fromstring–First issue date to include, YYYY-MM-DD
limitinteger–Maximum notes listed, default and ceiling 2000
reasonstring–Only notes with this reason
recipientstring–Match the recipient, case-insensitive, a part of the name is enough
statusstring–Only drafts or only finalized notes
tostring–Last issue date to include, YYYY-MM-DD

No output schema declared.

No examples provided.

credit_note_render ~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.

NameTypeReqDescription
formatstring–markdown (default) or html, a self-contained printable page
idstringyesThe credit note number CN-2026-0001 or draft id CN-DRAFT-2026-0001

No output schema declared.

No examples provided.

credit_note_summary ~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.

NameTypeReqDescription
fromstring–First issue date to include, YYYY-MM-DD. Default: the beginning
tostring–Last issue date to include, YYYY-MM-DD. Default: today

No output schema declared.

No examples provided.

credit_note_update ~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.

NameTypeReqDescription
currencystring–ISO code. Changing it reprices nothing: the stored minor units carry over, so only change it to fix a wrong currency
idstringyesThe draft id, e.g. CN-DRAFT-2026-0001
invoice_ref––New invoice reference, or null to detach the note from its invoice
issue_datestring––
linesarray–The full new line set, replacing every existing line
notes––New notes text, or null to remove the notes
reasonstring––
reason_detail–––
recipientstring––

No output schema declared.

No examples provided.

license_activate ~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.

NameTypeReqDescription
keystringyesLicense key from checkout, MCPL1.<payload>.<signature>

No output schema declared.

No examples provided.

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.

Install

How do I install the io.github.theluckystrike/credit-note MCP server?

io.github.theluckystrike/credit-note is a hosted endpoint at https://mcp.zovo.one/mcp/credit-note-ics, 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

# add to Claude Code
claude mcp add --transport http theluckystrike-credit-note 'https://mcp.zovo.one/mcp/credit-note-ics'
Common questions

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

io.github.theluckystrike/credit-note is an MCP server listed in the public MCP registry as io.github.theluckystrike/credit-note. Credit notes against an invoice or standalone: drafts, finalization, rendering, totals. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/credit-note-ics).

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

io.github.theluckystrike/credit-note scores 81 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-note MCP server expose?

io.github.theluckystrike/credit-note 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-note MCP server require authentication?

No. We connected to io.github.theluckystrike/credit-note without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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

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

What did VerifyMCP test on the io.github.theluckystrike/credit-note MCP server?

VerifyMCP ran 13 checks on io.github.theluckystrike/credit-note, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.