# io.github.theluckystrike/goods-receipt (remote · mcp.zovo.one)

Goods receipt notes vs purchase orders: tolerances, damaged/short units, CSV export.

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

## Components

- remote · `mcp.zovo.one`: 79/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-goods-receipt/mcp-goods-receipt.md), [page](https://verifymcp.io/servers/theluckystrike-goods-receipt/mcp-goods-receipt)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/goods-receipt`
- 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-21.

- **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**: 87/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).
  - Tool/resource definitions use about 1065 tokens (~88/item across 12 items; 11 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 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.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http theluckystrike-goods-receipt 'https://mcp.zovo.one/mcp/goods-receipt'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-goods-receipt": {
      "url": "https://mcp.zovo.one/mcp/goods-receipt"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-goods-receipt": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/goods-receipt"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-goods-receipt]
url = "https://mcp.zovo.one/mcp/goods-receipt"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add theluckystrike-goods-receipt --url 'https://mcp.zovo.one/mcp/goods-receipt' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-goods-receipt:
    url: "https://mcp.zovo.one/mcp/goods-receipt"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-goods-receipt": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/goods-receipt"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-goods-receipt -t streamable-http -u 'https://mcp.zovo.one/mcp/goods-receipt'
```

### Other

```json
{
  "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.

## 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-21 (score 79, +54)

- [security regression] Authorization: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] 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

### 2026-09-20 (score 25)

First indexed and scored.

## MCP tools (11)

### `po_add` (~139 tokens)

Add a purchase order

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.

Input parameters:

- `lines` (array, required): Lines on this purchase order
- `overTolerancePct` (integer): Whole % extra allowed above ordered (default 10)
- `reference` (string, required): Your own purchase-order number
- `supplier` (string, required): Who you ordered from
- `underTolerancePct` (integer): Whole % short allowed below ordered (default 10)

### `grn_add` (~181 tokens)

Receive goods against a purchase order

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.

Input parameters:

- `carrier` (string): Delivered by
- `lines` (array, required): Which PO lines you are receiving now
- `note` (string): Memo for the whole GRN
- `po` (string, required): Purchase-order id or reference, e.g. PO-0001
- `receivedAt` (string): ISO date of physical receipt (default today)

### `grn_line_add` (~157 tokens)

Add a line to an open GRN

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.

Input parameters:

- `damageNote` (string): What was damaged
- `damaged` (integer): Whole units received but damaged
- `grn` (string, required): Open GRN id, e.g. GRN-0001
- `line` (string, required): PO line to receive, e.g. L01
- `received` (integer, required): Whole units of good stock
- `shortageNote` (string): Why it is short

### `grn_list` (~51 tokens)

List goods-receipt notes

List goods-receipt notes, newest first, optionally filtered to one purchase order.

Input parameters:

- `includeLines` (boolean): Include line detail
- `po` (string): Only GRNs against this purchase order

### `grn_get` (~50 tokens)

Get one goods-receipt note

Get a single goods-receipt note by id, with its lines, damage and shortage per line.

Input parameters:

- `grn` (string, required): GRN id, e.g. GRN-0001

### `grn_discrepancy` (~73 tokens)

List discrepancies

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.

Input parameters:

- `includeResolved` (boolean): Include GRNs that are closed (resolved)
- `po` (string): Only discrepancies on this purchase order

### `grn_close` (~65 tokens)

Close a goods-receipt note

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.

Input parameters:

- `grn` (string, required): Open GRN id, e.g. GRN-0001

### `grn_status_report` (~79 tokens)

Goods-receipt status report

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.

Input parameters:

- `includeOnlyDiscrepancies` (boolean): Only list POs with at least one discrepancy

### `grn_export_csv` (~86 tokens)

Export goods receipts as CSV

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.

Input parameters:

- `po` (string): Export GRNs for one purchase order only

### `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-goods-receipt/mcp-goods-receipt#diagnostics

## Score history

- 2026-09-21: 79
- 2026-09-20: 25

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/goods-receipt
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/goods-receipt
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/goods-receipt
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-goods-receipt/mcp-goods-receipt.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-goods-receipt/mcp-goods-receipt.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-goods-receipt/mcp-goods-receipt