io.github.theluckystrike/goods-receipt
REMOTE · MCP.ZOVO.ONE · SCANNED SEP 21
Goods receipt notes vs purchase orders: tolerances, damaged/short units, CSV export.
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 1065 tokens (~88/item across 12 items; 11 tools + 1 resources), lean.Pass
- 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 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.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
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the io.github.theluckystrike/goods-receipt MCP server?
io.github.theluckystrike/goods-receipt is a hosted endpoint at https://mcp.zovo.one/mcp/goods-receipt, 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-goods-receipt 'https://mcp.zovo.one/mcp/goods-receipt'
{
"mcpServers": {
"theluckystrike-goods-receipt": {
"url": "https://mcp.zovo.one/mcp/goods-receipt"
}
}
} {
"servers": {
"theluckystrike-goods-receipt": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/goods-receipt"
}
}
} [mcp_servers.theluckystrike-goods-receipt] url = "https://mcp.zovo.one/mcp/goods-receipt"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-goods-receipt": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/goods-receipt",
"enabled": true
}
}
} openclaw mcp add theluckystrike-goods-receipt --url 'https://mcp.zovo.one/mcp/goods-receipt' --transport streamable-http
mcp_servers:
theluckystrike-goods-receipt:
url: "https://mcp.zovo.one/mcp/goods-receipt" {
"McpServers": {
"theluckystrike-goods-receipt": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/goods-receipt"
}
}
} assistant mcp add theluckystrike-goods-receipt -t streamable-http -u 'https://mcp.zovo.one/mcp/goods-receipt'
{
"mcpServers": {
"theluckystrike-goods-receipt": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/goods-receipt"
}
}
} 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.
- 21 Sept 26 +54
- Authorization: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 20 Sept 26 25
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 · Probed https://mcp.zovo.one/mcp/goods-receipt
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/goods-receipt | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/goods-receipt | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/goods-receipt |
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 →
grn_add Receive goods against a purchase order ~181
Create a goods-receipt note (GRN) against an open purchase order. Give one cell per PO line: the whole units received and/or damaged. received is checked against the line's ordered quantity and the PO's over tolerance; receiving past the over tolerance is refused unless declared damaged. Shortage is recorded automatically (ordered minus received, floored at zero) and shown as a discrepancy. Partial deliveries are fine: raise several GRNs against the same PO. Free tier, full CRUD.
| Name | Type | Req | Description |
|---|---|---|---|
| carrier | string | – | Delivered by |
| lines | array | yes | Which PO lines you are receiving now |
| note | string | – | Memo for the whole GRN |
| po | string | yes | Purchase-order id or reference, e.g. PO-0001 |
| receivedAt | string | – | ISO date of physical receipt (default today) |
No output schema declared.
No examples provided.
grn_close Close a goods-receipt note ~65
Close an open GRN. A closed GRN can no longer take lines, and its discrepancies are treated as resolved. Closing is free-tier and never mutates the PO.
| Name | Type | Req | Description |
|---|---|---|---|
| grn | string | yes | Open GRN id, e.g. GRN-0001 |
No output schema declared.
No examples provided.
grn_discrepancy List discrepancies ~73
List lines that are not as ordered: damaged units, a declared shortage, or received below the PO line's under tolerance. Optionally filter to one PO.
| Name | Type | Req | Description |
|---|---|---|---|
| includeResolved | boolean | – | Include GRNs that are closed (resolved) |
| po | string | – | Only discrepancies on this purchase order |
No output schema declared.
No examples provided.
grn_export_csv Export goods receipts as CSV ~86
Pro. Export every GRN (or just one PO's GRNs) as CSV with a header row: grn,po,po_reference,received_at,carrier,status,line,sku,received,damaged,shortage,damage_note,shortage_note. Watermark-free and not truncated.
| Name | Type | Req | Description |
|---|---|---|---|
| po | string | – | Export GRNs for one purchase order only |
No output schema declared.
No examples provided.
grn_get Get one goods-receipt note ~50
Get a single goods-receipt note by id, with its lines, damage and shortage per line.
| Name | Type | Req | Description |
|---|---|---|---|
| grn | string | yes | GRN id, e.g. GRN-0001 |
No output schema declared.
No examples provided.
grn_line_add Add a line to an open GRN ~157
Add another PO line (or more units on a line already open on this GRN) to an existing open goods-receipt note. Useful when one delivery arrives in batches. The over-tolerance gate still applies to the PO line's cumulative received count across every GRN. Free tier, full CRUD.
| Name | Type | Req | Description |
|---|---|---|---|
| damageNote | string | – | What was damaged |
| damaged | integer | – | Whole units received but damaged |
| grn | string | yes | Open GRN id, e.g. GRN-0001 |
| line | string | yes | PO line to receive, e.g. L01 |
| received | integer | yes | Whole units of good stock |
| shortageNote | string | – | Why it is short |
No output schema declared.
No examples provided.
grn_list List goods-receipt notes ~51
List goods-receipt notes, newest first, optionally filtered to one purchase order.
| Name | Type | Req | Description |
|---|---|---|---|
| includeLines | boolean | – | Include line detail |
| po | string | – | Only GRNs against this purchase order |
No output schema declared.
No examples provided.
grn_status_report Goods-receipt status report ~79
Reconcile every purchase order against every GRN: open POs (not yet fully received), POs fully received within tolerance, POs with at least one discrepancy, and per-line open/short/damaged counts. Nothing is written.
| Name | Type | Req | Description |
|---|---|---|---|
| includeOnlyDiscrepancies | boolean | – | Only list POs with at least one discrepancy |
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.
po_add Add a purchase order ~139
Create a purchase order to receive goods against. Lines carry a sku, a description and an ordered whole-unit quantity. Over/under tolerances are whole percentages allowed above/below ordered before a GRN is flagged. Ids look like PO-0001. Free tier, full CRUD.
| Name | Type | Req | Description |
|---|---|---|---|
| lines | array | yes | Lines on this purchase order |
| overTolerancePct | integer | – | Whole % extra allowed above ordered (default 10) |
| reference | string | yes | Your own purchase-order number |
| supplier | string | yes | Who you ordered from |
| underTolerancePct | integer | – | Whole % short allowed below ordered (default 10) |
No output schema declared.
No examples provided.
What is the io.github.theluckystrike/goods-receipt MCP server?
io.github.theluckystrike/goods-receipt is an MCP server listed in the public MCP registry as io.github.theluckystrike/goods-receipt. Goods receipt notes vs purchase orders: tolerances, damaged/short units, CSV export. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/goods-receipt).
Is the io.github.theluckystrike/goods-receipt MCP server safe to use?
io.github.theluckystrike/goods-receipt 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/goods-receipt MCP server expose?
io.github.theluckystrike/goods-receipt exposes 11 tools: po_add, grn_add, grn_line_add, grn_list, grn_get, and 6 more. Their descriptions and schemas cost roughly 1,012 tokens of context every time the server is loaded.
Does the io.github.theluckystrike/goods-receipt MCP server require authentication?
Yes. io.github.theluckystrike/goods-receipt 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/goods-receipt MCP server still maintained?
io.github.theluckystrike/goods-receipt is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.