Dicker Data
OCI · GHCR.IO/WYRE-AI/DICKER-DATA-MCP
MCP server for Dicker Data's B2B partner/reseller REST API — pricing, orders, and invoices.
Available components
Last scanned (8 hours ago)
Scores higher than 50% of OCI 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 Security0
- 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 could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency32
- 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
- License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 537 tokens (~59/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 43% 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
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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.
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.
- 17 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 15 Oct 26 +30
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Tool coverage: 43 functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- 14 Oct 26 6
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 18 Oct 2026 · Analysed oci/ghcr.io/wyre-ai/dicker-data-mcp@v1.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
dickerdata_create_order ~95
Place a new purchase order with Dicker Data for one or more products.
| Name | Type | Req | Description |
|---|---|---|---|
| customerPORef | string | – | Your own purchase-order reference for this order. |
| deliveryAddress | object | – | Delivery address. Omit to ship to the account default address. |
| deliveryAttention | string | – | Attention line for delivery. |
| items | array | yes | Products to order. |
| notes | string | – | Order-level notes. |
No output schema declared.
No examples provided.
dickerdata_get_consignment_status ~36
Get shipping/tracking status for a Dicker Data consignment number.
| Name | Type | Req | Description |
|---|---|---|---|
| consignmentNumber | string | yes | – |
No output schema declared.
No examples provided.
dickerdata_get_invoice_details ~54
Get line-item detail for a Dicker Data sales order / invoice.
| Name | Type | Req | Description |
|---|---|---|---|
| includeCustomerQualification | boolean | – | – |
| salesOrderNumber | string | yes | – |
| salesOrderNumberSuffix | string | – | – |
No output schema declared.
No examples provided.
dickerdata_get_order_details ~58
Get details for a single Dicker Data order by order number, account code, or your PO reference.
| Name | Type | Req | Description |
|---|---|---|---|
| accountCode | string | – | – |
| customerPORef | string | – | – |
| orderNumber | string | – | – |
No output schema declared.
No examples provided.
dickerdata_get_order_serials ~41
Get the shipped serial numbers for a Dicker Data order.
| Name | Type | Req | Description |
|---|---|---|---|
| orderNumber | string | yes | – |
| orderSuffix | string | – | – |
No output schema declared.
No examples provided.
dickerdata_get_price ~63
Get detailed pricing for a single Dicker Data product code at a given quantity.
| Name | Type | Req | Description |
|---|---|---|---|
| productCode | string | yes | The Dicker Data product/part number to price. |
| quantity | number | – | Quantity to price at. Defaults to 1 if omitted. |
No output schema declared.
No examples provided.
dickerdata_get_pricing ~57
Look up live pricing and stock-on-hand for one or more Dicker Data product codes (part numbers).
| Name | Type | Req | Description |
|---|---|---|---|
| productCodes | array | yes | One or more Dicker Data product/part numbers to price and check stock for. |
No output schema declared.
No examples provided.
dickerdata_list_invoices ~65
List Dicker Data account invoices within a date range.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | – | End date, e.g. 2026-01-31. |
| startDate | string | – | Start date, e.g. 2026-01-01. |
No output schema declared.
No examples provided.
dickerdata_list_orders ~68
List Dicker Data orders matching an account code, order number, backorder number, or customer PO number.
| Name | Type | Req | Description |
|---|---|---|---|
| accountCode | string | – | – |
| backorderNumber | string | – | – |
| customerPONumber | string | – | – |
| orderNumber | string | – | – |
No output schema declared.
No examples provided.
How do I install the Dicker Data MCP server?
Dicker Data runs locally as a container image, launched with docker run --rm -i -e DICKERDATA_ACCOUNT_CODE -e DICKERDATA_ACCESS_TOKEN -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/dicker-data-mcp:v1.0.3. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/wyre-ai/dicker-data-mcp
claude mcp add wyre-ai-dicker-data-mcp -- docker run --rm -i -e DICKERDATA_ACCOUNT_CODE -e DICKERDATA_ACCESS_TOKEN -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/dicker-data-mcp:v1.0.3
This image reads DICKERDATA_ACCOUNT_CODE, DICKERDATA_ACCESS_TOKEN, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the Dicker Data MCP server?
Dicker Data is an MCP server listed in the public MCP registry as io.github.WYRE-AI/dicker-data-mcp. MCP server for Dicker Data's B2B partner/reseller REST API, pricing, orders, and invoices. This page covers its container image (ghcr.io/wyre-ai/dicker-data-mcp).
Is the Dicker Data MCP server safe to use?
Dicker Data scores 37 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 Dicker Data MCP server expose?
Dicker Data exposes 9 tools: dickerdata_get_pricing, dickerdata_get_price, dickerdata_create_order, dickerdata_get_order_details, dickerdata_list_orders, and 4 more. Their descriptions and schemas cost roughly 537 tokens of context every time the server is loaded.
Is the Dicker Data MCP server still maintained?
Dicker Data is still listed as active in the MCP registry. We last reached this channel on 18 October 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 Dicker Data MCP server under?
Dicker Data declares the NOASSERTION licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.