# io.github.theluckystrike/supplier-statement-check (mcpb · supplier-statement-check.mcpb)

Compare supplied supplier statement and AP open items locally, with complete discrepancy evidence.

- Trust score: 48/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `supplier-statement-check.mcpb`: 48/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-supplier-statement-check/supplier-statement-check.md), [page](https://verifymcp.io/servers/theluckystrike-supplier-statement-check/supplier-statement-check)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.25.0/supplier-statement-check.mcpb`
- Version: `0.25.0`
- Transport: `stdio`
- SHA-256: `98784c618a5f7df7c0e3ea4d4528200c10ea43d65eff785fbc1cde55216b306b`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-11-05.

- **Supply Chain Security**: 23/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 444 tokens (~55/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 69/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 8% 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 8 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.

## Install

### How do I install the io.github.theluckystrike/supplier-statement-check MCP server?

io.github.theluckystrike/supplier-statement-check ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 98784c618a5f7df7c0e3ea4d4528200c10ea43d65eff785fbc1cde55216b306b; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.25.0/supplier-statement-check.mcpb`
- SHA-256: `98784c618a5f7df7c0e3ea4d4528200c10ea43d65eff785fbc1cde55216b306b`

### Verify on macOS / Linux

```bash
echo "98784c618a5f7df7c0e3ea4d4528200c10ea43d65eff785fbc1cde55216b306b  supplier-statement-check.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\supplier-statement-check.mcpb).Hash -eq "98784c618a5f7df7c0e3ea4d4528200c10ea43d65eff785fbc1cde55216b306b"
```

## 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-11-04 (score 48, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 47, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 46, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 45, +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.

### 2026-10-27 (score 44, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 43)

First indexed and scored.

## MCP tools (8)

### `supplier_statement_check` (~60 tokens)

Compare supplier statement and AP open items

Compare two supplied open-item lists of up to 1000 records each by exact entity, supplier, currency, document type and reference. Flag missing-side items, amount/date discrepancies and ambiguous repeated references. All evidence is free; no balance or payment approval.

### `report_list` (~46 tokens)

List saved open-item checks

List saved report ids, timestamps and review-group counts. Free on both tiers; up to 100 reports per page.

Input parameters:

- `limit` (integer)
- `offset` (integer)

### `report_get` (~31 tokens)

Read a saved open-item check

Read a saved comparison with complete source evidence. Large reports return free paging instructions.

Input parameters:

- `id` (string, required)

### `report_page` (~77 tokens)

Read complete open-item evidence pages

Read free pages of either source list, group summaries or one group’s source members. Unsaved previews last 30 minutes for the last two checks in this process.

Input parameters:

- `group_id` (string)
- `id` (string, required)
- `limit` (integer)
- `offset` (integer)
- `section` (string, required)

### `report_delete` (~33 tokens)

Delete one saved open-item check

Delete one local comparison report and free a saved-report slot. Does not alter accounting records.

Input parameters:

- `id` (string, required)

### `report_export_csv` (~72 tokens)

Export complete open-item evidence as CSV

Export free CSV pages from a saved report or unsaved preview. One row per supplied source item, with side, group and issues. Formula-like cells are escaped; no amount-loss or balance total is calculated.

Input parameters:

- `id` (string, required)
- `limit` (integer)
- `offset` (integer)

### `license_status` (~54 tokens)

License status

Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.

### `license_activate` (~71 tokens)

Activate license

Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.

Input parameters:

- `key` (string, required): License key from the checkout confirmation page

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/theluckystrike-supplier-statement-check/supplier-statement-check#diagnostics

## Score history

- 2026-11-05: 48
- 2026-11-04: 48
- 2026-11-03: 47
- 2026-11-02: 47
- 2026-11-01: 46
- 2026-10-31: 46
- 2026-10-30: 45
- 2026-10-29: 45
- 2026-10-28: 44
- 2026-10-27: 44
- 2026-10-26: 43

## Common questions

### What is the io.github.theluckystrike/supplier-statement-check MCP server?

io.github.theluckystrike/supplier-statement-check is an MCP server listed in the public MCP registry as io.github.theluckystrike/supplier-statement-check. Compare supplied supplier statement and AP open items locally, with complete discrepancy evidence. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.25.0/supplier-statement-check.mcpb).

### Is the io.github.theluckystrike/supplier-statement-check MCP server safe to use?

io.github.theluckystrike/supplier-statement-check scores 48 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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/supplier-statement-check MCP server expose?

io.github.theluckystrike/supplier-statement-check exposes 8 tools: supplier_statement_check, report_list, report_get, report_page, report_delete, and 3 more. Their descriptions and schemas cost roughly 444 tokens of context every time the server is loaded.

### What licence is the io.github.theluckystrike/supplier-statement-check MCP server under?

io.github.theluckystrike/supplier-statement-check declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.theluckystrike/supplier-statement-check MCP server?

VerifyMCP ran 15 checks on io.github.theluckystrike/supplier-statement-check, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.theluckystrike/supplier-statement-check: Malware scan. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/supplier-statement-check?utm_source=mcp-registry&utm_medium=registry&utm_campaign=supplier-statement-check
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-supplier-statement-check/supplier-statement-check.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-supplier-statement-check/supplier-statement-check/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-supplier-statement-check/supplier-statement-check.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-supplier-statement-check/supplier-statement-check