io.github.theluckystrike/billing-docs-credit-notes-purchase-orders
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20
Credit notes against your invoices and purchase orders to suppliers, with VAT and A4 PDFs.
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 Usability87
- 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
- Tool/resource definitions use about 1888 tokens (~104/item across 18 items; 16 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 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 17 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/billing-docs-credit-notes-purchase… MCP server?
io.github.theluckystrike/billing-docs-credit-notes-purchase… is a hosted endpoint at https://mcp.zovo.one/mcp/billing-docs, 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-billing-docs-credit-notes-purchas 'https://mcp.zovo.one/mcp/billing-docs'
{
"mcpServers": {
"theluckystrike-billing-docs-credit-notes-purchas": {
"url": "https://mcp.zovo.one/mcp/billing-docs"
}
}
} {
"servers": {
"theluckystrike-billing-docs-credit-notes-purchas": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/billing-docs"
}
}
} [mcp_servers.theluckystrike-billing-docs-credit-notes-purchas] url = "https://mcp.zovo.one/mcp/billing-docs"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-billing-docs-credit-notes-purchas": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/billing-docs",
"enabled": true
}
}
} openclaw mcp add theluckystrike-billing-docs-credit-notes-purchas --url 'https://mcp.zovo.one/mcp/billing-docs' --transport streamable-http
mcp_servers:
theluckystrike-billing-docs-credit-notes-purchas:
url: "https://mcp.zovo.one/mcp/billing-docs" {
"McpServers": {
"theluckystrike-billing-docs-credit-notes-purchas": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/billing-docs"
}
}
} assistant mcp add theluckystrike-billing-docs-credit-notes-purchas -t streamable-http -u 'https://mcp.zovo.one/mcp/billing-docs'
{
"mcpServers": {
"theluckystrike-billing-docs-credit-notes-purchas": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/billing-docs"
}
}
} 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 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +57
- Authorization: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Transport: unverified → pass ▲ security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Stability: unverified → 0.30 ▲ functional
- 17 Sept 26 −56
- Endpoint reachability: reachable → behind authorisation ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.23 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Server version: 0.21.0 → 0.22.0 functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
- Tool “purchase_order_create” rewrote its description, which is the text the model reads security
- Tool “license_activate” rewrote its description, which is the text the model reads security
- Schema quality: fail → pass ▲ functional
- New prompt “upgrade_to_pro” functional
- New resource “pricing” functional
- 10 Sept 26 +1
- Tool “credit_note_text” rewrote its description, which is the text the model reads security
- Tool “license_activate” rewrote its description, which is the text the model reads security
- Tool “license_status” rewrote its description, which is the text the model reads security
- Tool “purchase_order_create” rewrote its description, which is the text the model reads security
- Tool “purchase_order_pdf” rewrote its description, which is the text the model reads security
- Tool “purchase_order_get” rewrote its description, which is the text the model reads security
- Tool “purchase_order_list” rewrote its description, which is the text the model reads security
- Tool “purchase_order_receive” rewrote its description, which is the text the model reads security
- Tool “purchase_order_delete” rewrote its description, which is the text the model reads security
- Tool “purchase_order_text” rewrote its description, which is the text the model reads security
- Tool “billing_docs_report” rewrote its description, which is the text the model reads security
- Tool “credit_note_create” rewrote its description, which is the text the model reads security
- Tool “credit_note_delete” rewrote its description, which is the text the model reads security
- Tool “credit_note_get” rewrote its description, which is the text the model reads security
- Tool “credit_note_list” rewrote its description, which is the text the model reads security
- Tool “credit_note_pdf” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- “license_activate” reworded the description of “key” cosmetic
- 9 Sept 26 +41
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: 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. security
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 0 functional
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/billing-docs
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/billing-docs | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/billing-docs | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/billing-docs |
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 →
billing_docs_report Credited money and open orders ~86
Over a date range: what was credited back per currency and against how many invoices, what is still on order per currency, and every open order past its delivery date with days late. Pro; the list tools are free.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | YYYY-MM-DD, earliest document date to count |
| to | string | – | YYYY-MM-DD, latest document date to count |
No output schema declared.
No examples provided.
credit_note_create Credit an invoice ~209
Credit one invoice: the whole invoice, a GROSS amount_minor split over its VAT rates, or named lines. Amounts store negative, reusing the invoice's own rates. Free: 5 a month. Send it with credit_note_text.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_minor | integer | – | Credit this GROSS amount, VAT included, in minor units. Split across the invoice's VAT rates in proportion to each rate's share of the total |
| invoice | string | yes | The invoice number to credit, e.g. INV-2026-0001 |
| issue_date | string | – | YYYY-MM-DD, defaults to today in your business profile's timezone |
| lines | array | – | Credit only these invoice lines. Leave out with amount_minor for a full credit note |
| notes | string | – | Free text printed under the totals |
| reason | string | yes | Why the money is being given back, e.g. "returned goods" or "billed twice". Printed on the document |
No output schema declared.
No examples provided.
credit_note_delete Delete a credit note ~76
Remove one credit note never posted to its invoice and never rendered, freeing that month's slot; the invoice becomes creditable again. One with a dependent is refused: issue a fresh note to reverse a sent one.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Credit note id such as CN-2026-0001, or an exact client name |
No output schema declared.
No examples provided.
credit_note_get Show one credit note ~81
Return one credit note in full by id or exact client name: every negated line, VAT lines, totals, the reason, and the invoice number and date it reverses. Reads only. Use credit_note_list for the ids.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Credit note id such as CN-2026-0001, or an exact client name |
No output schema declared.
No examples provided.
credit_note_list List credit notes ~109
List credit notes newest first: id, invoice, client, basis, reason, currency and the NEGATIVE total, with the amount credited per currency. Filter by invoice, client or issue date range.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Only credit notes for clients whose name contains this text |
| from | string | – | YYYY-MM-DD, earliest issue date |
| invoice | string | – | Only credit notes issued against this invoice number |
| to | string | – | YYYY-MM-DD, latest issue date |
No output schema declared.
No examples provided.
credit_note_pdf Render the credit note as a PDF ~108
Call this tool to render one credit note as an A4 print-ready document and return a download link valid for one hour: the invoice layout titled CREDIT NOTE, with the invoice it reverses. Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Credit note id such as CN-2026-0001 |
| out_path | string | – | Name for the downloaded file, e.g. acme-credit. Defaults to the document id; the document comes back as a download link valid for one hour |
No output schema declared.
No examples provided.
credit_note_text Plain-text credit note to paste into email ~122
Turn a credit note into a plain-text summary to paste into an email: the negated line table, VAT lines, total, reason, and what now comes off the invoice. Also a .txt download link valid one hour. Free; credit_note_pdf writes the A4 document.
| Name | Type | Req | Description |
|---|---|---|---|
| greeting | string | – | Opening line, default "Hello" plus the client name |
| id | string | yes | Credit note id such as CN-2026-0001 |
| sign_off | string | – | Closing line, default your business name from the shared profile |
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.
purchase_order_create Raise a purchase order ~271
Raise a purchase order to a supplier from items and return its PO number and totals. unit_price is in MAJOR units; currency, VAT and the buyer block come from the shared profile. Free: 5 documents a calendar month.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Defaults to your business default currency |
| discount_percent | number | – | Discount applied to every line, in percent |
| expected_delivery_date | string | – | YYYY-MM-DD, when the goods or work are due |
| issue_date | string | – | YYYY-MM-DD, defaults to today in your business profile's timezone |
| items | array | yes | What is being ordered |
| notes | string | – | Free text printed under the totals, e.g. delivery address or terms |
| supplier | string | yes | Supplier name or client id. A name the invoice server already knows brings its address, email and VAT id onto the order |
| supplier_address | string | – | Postal address for the SUPPLIER block, newlines allowed |
| supplier_email | string | – | Only if the user gave it; otherwise the stored client's email is used |
| supplier_vat_id | string | – | Supplier VAT / tax registration id |
| tax_rate | number | – | VAT percent for lines with no rate of their own. Defaults to the business default |
No output schema declared.
No examples provided.
purchase_order_delete Delete a purchase order ~74
Remove one purchase order with nothing received and never rendered, freeing that month's slot. One with a receipt is refused, naming it. The PO number is never reissued. purchase_order_receive logs arrivals.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Purchase order id such as PO-2026-0001, or an exact supplier name |
No output schema declared.
No examples provided.
purchase_order_get Show one purchase order ~76
Return one purchase order in full by id or exact supplier name: buyer and supplier blocks, every line with unit price and VAT, totals, the delivery date, status and every receipt with its date and note.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Purchase order id such as PO-2026-0001, or an exact supplier name |
No output schema declared.
No examples provided.
purchase_order_list List purchase orders ~103
List purchase orders newest first: id, supplier, order and expected delivery dates, status open, partially_received or received, currency, total and received date. Filter by status, supplier or date range.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | YYYY-MM-DD, earliest order date |
| status | string | – | Default "all" |
| supplier | string | – | Only orders to suppliers whose name contains this text |
| to | string | – | YYYY-MM-DD, latest order date |
No output schema declared.
No examples provided.
purchase_order_pdf Render the purchase order as a PDF ~107
Call this tool to render one purchase order as an A4 print-ready document and return a download link valid for one hour: the invoice layout titled PURCHASE ORDER, with the buyer and supplier. Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Purchase order id such as PO-2026-0001 |
| out_path | string | – | Name for the downloaded file, e.g. acme-credit. Defaults to the document id; the document comes back as a download link valid for one hour |
No output schema declared.
No examples provided.
purchase_order_receive Mark a purchase order received ~141
Record that an order arrived. partial keeps it open and can be repeated, each receipt kept with its date and note; a full receipt closes it. An order already received, or a date before the order date, is refused.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | YYYY-MM-DD, defaults to today |
| id | string | yes | Purchase order id such as PO-2026-0001 |
| note | string | – | What arrived, e.g. "8 of 10 units, 2 back-ordered" |
| partial | boolean | – | True when only some of the order arrived. The order stays open and can be received again. Default false |
No output schema declared.
No examples provided.
purchase_order_text Plain-text purchase order to paste into email ~121
Turn a purchase order into a plain-text order to paste into an email: the line table, VAT lines, total, and a line asking the supplier to deliver by the date and quote the PO number. Also a .txt download link valid one hour. Free on every tier.
| Name | Type | Req | Description |
|---|---|---|---|
| greeting | string | – | Opening line, default "Hello" plus the supplier name |
| id | string | yes | Purchase order id such as PO-2026-0001 |
| sign_off | string | – | Closing line, default your business name from the shared profile |
No output schema declared.
No examples provided.
What is the io.github.theluckystrike/billing-docs-credit-notes-purchase… MCP server?
io.github.theluckystrike/billing-docs-credit-notes-purchase… is an MCP server listed in the public MCP registry as io.github.theluckystrike/billing-docs-credit-notes-purchase…. Credit notes against your invoices and purchase orders to suppliers, with VAT and A4 PDFs. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/billing-docs).
Is the io.github.theluckystrike/billing-docs-credit-notes-purchase… MCP server safe to use?
io.github.theluckystrike/billing-docs-credit-notes-purchase… scores 83 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/billing-docs-credit-notes-purchase… MCP server expose?
io.github.theluckystrike/billing-docs-credit-notes-purchase… exposes 16 tools: credit_note_create, credit_note_list, credit_note_get, credit_note_pdf, credit_note_text, and 11 more. Their descriptions and schemas cost roughly 1,815 tokens of context every time the server is loaded.
Does the io.github.theluckystrike/billing-docs-credit-notes-purchase… MCP server require authentication?
Yes. io.github.theluckystrike/billing-docs-credit-notes-purchase… 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/billing-docs-credit-notes-purchase… MCP server still maintained?
io.github.theluckystrike/billing-docs-credit-notes-purchase… 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.