Delhaize receipts
PYPI · DELHAIZE-MCP
Fetch your own Delhaize (Belgium) till receipts and weekly promotions with a headless browser.
Available components
Last scanned (18 hours ago)
Scores higher than 82% of PyPI servers
Category E-commerce
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs uv_build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 31 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 33 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 618 tokens (~123/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 −14
- Malware scan: pass → unverified ▼ security
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 4 Nov 2026 · Analysed pypi/delhaize-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | uv_build |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
delhaize_auth_status ~74
Check whether the saved Delhaize browser profile is still logged in. Returns {logged_in: bool, message: str}. If logged_in is false, the user must run `delhaize-receipts login` once to refresh the session; this server cannot and must not perform the login itself.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
delhaize_backfill_images ~148
Save the missing PHOTOS of Delhaize receipts that are already in the record but have no image. A receipt lacks a photo when its record has no existing `image` path and no matching file is already in receipts_backfill/. Not read only: it writes image files into receipts_backfill/. It never edits receipts_all.json and never uses receipts_inbox, so nothing is ingested twice. Each file is named '<date> <store> <total>' so it pairs with its receipt. Returns {missing, found, saved:[...], missed:[...], not_in_window:[...], next_step}.
| Name | Type | Req | Description |
|---|---|---|---|
| months_back | integer | – | – |
No output schema declared.
No examples provided.
delhaize_fetch_new_receipts ~172
Save the images of any NEW Delhaize receipts (this month and the previous `months_back` months) into receipts_inbox, ready for the existing pipeline. Not read only: it writes image files into receipts_inbox. It is non destructive: it never overwrites, never deletes, and never edits receipts_all.json. A receipt already present in receipts_all.json is skipped. After it runs, the images can be read (by the assistant or any OCR) and recorded in receipts_all.json by your own process; checking that the lines sum to the printed total before recording is strongly recommended. Returns {new_count, saved:[{date, store, total, path}], missed:[...], next_step}.
| Name | Type | Req | Description |
|---|---|---|---|
| months_back | integer | – | – |
No output schema declared.
No examples provided.
delhaize_fetch_promotions ~107
Read this week's public Delhaize promotions listing (store context from the saved profile) and save each page's raw data into promos_inbox/<today>/. Not read only: it writes JSON files into promos_inbox. It never edits anything else and never judges products; parsing the capture is left to your own code. Returns {pages, tiles, api_bodies, out_dir, stopped, next_step}.
| Name | Type | Req | Description |
|---|---|---|---|
| max_pages | integer | – | – |
No output schema declared.
No examples provided.
delhaize_list_receipts ~117
List Delhaize receipts for the current month and the previous `months_back` months, flagging which are not yet in receipts_all.json. Read only: opens nothing and writes nothing. Use this to preview before fetching. months_back=1 (the default) covers this month and last, which is enough to catch a month boundary. Returns {count, new_count, receipts:[{date, store, total, points, savings, is_new}]}.
| Name | Type | Req | Description |
|---|---|---|---|
| months_back | integer | – | – |
No output schema declared.
No examples provided.
How do I install the Delhaize receipts MCP server?
Delhaize receipts runs locally as a PyPI package, launched with uvx delhaize-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · delhaize-mcp
claude mcp add shimabeigi-delhaize-mcp -- uvx delhaize-mcp
What is the Delhaize receipts MCP server?
Delhaize receipts is an MCP server listed in the public MCP registry as io.github.SHIMABEIGI/delhaize-mcp. Fetch your own Delhaize (Belgium) till receipts and weekly promotions with a headless browser. This page covers its PyPI package (delhaize-mcp).
Is the Delhaize receipts MCP server safe to use?
Delhaize receipts scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. 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 Delhaize receipts MCP server expose?
Delhaize receipts exposes 5 tools: delhaize_auth_status, delhaize_list_receipts, delhaize_fetch_new_receipts, delhaize_backfill_images, delhaize_fetch_promotions. Their descriptions and schemas cost roughly 618 tokens of context every time the server is loaded.
Is the Delhaize receipts MCP server still maintained?
Delhaize receipts is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Delhaize receipts MCP server under?
Delhaize receipts declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.