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/three-way-match

MCPB · THREE-WAY-MATCH.MCPB

Match supplier invoice lines against purchase orders and accepted receipts by SKU, locally.

45 Trust /100

Last scanned (19 hours ago)

Scores higher than 79% of MCPB servers

Category Finance and Payments

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security23
  • 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.Unverified
  • Known CVEs were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 547 tokens (~68/item across 8 items; 8 tools + 0 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 Coverage75
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 26% 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 8 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: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 16 Oct 26 45

    First indexed and scored.

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 18 Oct 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.8/three-way-match.mcpb@0.22.8

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~547 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
license_activate ~71

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.

NameTypeReqDescription
keystringyesLicense key from the checkout confirmation page

No output schema declared.

No examples provided.

license_status ~54

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

report_delete ~48

Delete one saved report by id, freeing a free-tier storage slot. Does not alter source documents or prior invoice history.

NameTypeReqDescription
idstringyesSaved UUID from report_list or three_way_match

No output schema declared.

No examples provided.

report_export_csv ~76

Return CSV of saved SKU quantities, prices and issues. Large CSVs paginate; follow next_offset with offset. Formula-like text is escaped. Full source evidence uses report_get/report_page.

NameTypeReqDescription
idstringyesSaved UUID from report_list or three_way_match
limitinteger––
offsetinteger––

No output schema declared.

No examples provided.

report_get ~45

Read a saved report with source documents, per-SKU evidence and all exceptions. Free on both tiers.

NameTypeReqDescription
idstringyesSaved UUID from report_list or three_way_match

No output schema declared.

No examples provided.

report_list ~53

List saved report ids, timestamps, document references, status and issue counts. Free on both tiers; paginated, up to 100 reports per call.

NameTypeReqDescription
limitinteger––
offsetinteger––

No output schema declared.

No examples provided.

report_page ~92

Read free pages of large report issues, SKU rows or original source rows. Use report_id from the paginated overview. Unsaved previews expire after 30 minutes and keep only the last two large checks.

NameTypeReqDescription
idstringyes–
limitinteger––
offsetinteger––
receipt_indexinteger––
sectionstringyes–
skustring––

No output schema declared.

No examples provided.

three_way_match ~108

Compare up to 500 PO/invoice lines by exact SKU, accepted receipts and prior billed quantities. Returns source evidence and exceptions, including offsetting errors. All diagnosis is free; save optionally.

NameTypeReqDescription
invoiceobjectyes–
poobjectyes–
prior_invoicedarrayyesCumulative previously invoiced whole units, excluding this invoice; [] explicitly asserts none. Caller must supply complete history.
receiptsarrayyes–
saveboolean––

No output schema declared.

No examples provided.

Install

How do I install the io.github.theluckystrike/three-way-match MCP server?

io.github.theluckystrike/three-way-match 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, 6397928ec44ea9d5c406a66f4eb7aa9a2f34f5731bf8ef9972fadfdac882f040; the commands to do that are on this page. If it does not match, do not open it.

mcpb · three-way-match.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

6397928ec44ea9d5c406a66f4eb7aa9a2f34f5731bf8ef9972fadfdac882f040

macOS / Linux

echo "6397928ec44ea9d5c406a66f4eb7aa9a2f34f5731bf8ef9972fadfdac882f040  three-way-match.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\three-way-match.mcpb).Hash -eq "6397928ec44ea9d5c406a66f4eb7aa9a2f34f5731bf8ef9972fadfdac882f040"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

Common questions

What is the io.github.theluckystrike/three-way-match MCP server?

io.github.theluckystrike/three-way-match is an MCP server listed in the public MCP registry as io.github.theluckystrike/three-way-match. Match supplier invoice lines against purchase orders and accepted receipts by SKU, locally. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.8/three-way-match.mcpb).

Is the io.github.theluckystrike/three-way-match MCP server safe to use?

io.github.theluckystrike/three-way-match scores 45 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/three-way-match MCP server expose?

io.github.theluckystrike/three-way-match exposes 8 tools: three_way_match, report_list, report_get, report_page, report_delete, and 3 more. Their descriptions and schemas cost roughly 547 tokens of context every time the server is loaded.

What licence is the io.github.theluckystrike/three-way-match MCP server under?

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