io.github.theluckystrike/supplier-list
MCPB · SUPPLIER-LIST.MCPB · 2 COMPONENTS · SCANNED SEP 20
A supplier directory that does not rot: contacts, terms, lead times, review dates.
Available components
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
- Malware scan not yet available for this package.Unverified
- Known CVEs were checked across the 96 of 96 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 96 dependencies flagged as unhealthy. View diagnostics → Partial
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 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 Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1244 tokens (~124/item across 10 items; 10 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "supplier_remove" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 10 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.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
mcpb · supplier-list.mcpb
Download bundleEvery 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 Sept 26 47
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 20 Sept 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/supplier-list.mcpb@0.22.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 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 →
license_activate Activate license ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from the checkout confirmation page |
No output schema declared.
No examples provided.
license_status 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.
supplier_add Add a supplier ~260
Add a supplier to the directory and return its SUP-YYYY-NNNN number: the name, what they supply, who to contact and how, the payment terms, the lead time in days, and notes. Free tier: 10 suppliers; removing one you no longer use frees its slot.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Postal or visiting address |
| category | string | yes | What they supply, e.g. Packaging, Raw materials, Print. Free-form; supplier_list filters on it |
| contact_name | string | – | Your person there, e.g. Maria Chen |
| string | – | Orders or accounts email | |
| lead_time_days | integer | – | Typical days from order to delivery, e.g. 14 |
| name | string | yes | Who you buy from, e.g. Shenzhen Box Co, or Acme Fasteners |
| notes | string | – | Anything worth remembering: minimum orders, who to escalate to, why you dropped them last time |
| payment_terms | string | – | The terms you buy on, e.g. Net 30, 50% upfront, Due on receipt |
| phone | string | – | Phone number as you would dial it |
| website | string | – | Website or storefront URL |
No output schema declared.
No examples provided.
supplier_due_review Which supplier records have gone stale ~91
The due-review report: every supplier whose record has not been reviewed in the last N days -- 90 unless you say otherwise -- most overdue first. A record never reviewed is always due, whatever its age. This is the report that keeps the directory from rotting. Pro feature.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | A record is due when its last review is older than this many days. Default 90 |
No output schema declared.
No examples provided.
supplier_export Export the directory ~122
Export the supplier directory as CSV or a Markdown table: every field, one row per supplier, A to Z by name. CSV opens in any spreadsheet; Markdown drops into a doc, a wiki or a README. Filter by category and free text first if you only want part of it. CSV is free; Markdown is Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Only suppliers in exactly this category, case-insensitive |
| format | string | – | csv (default) or markdown |
| q | string | – | Only suppliers whose fields contain this text, case-insensitive |
No output schema declared.
No examples provided.
supplier_get Read one supplier ~77
Read one supplier record in full by SUP number or name: every contact field, the payment terms, the lead time, the notes, and when the record was last reviewed. Reads only.
| Name | Type | Req | Description |
|---|---|---|---|
| supplier | string | yes | The supplier id, e.g. SUP-2026-0003, or the name when only one supplier has it |
No output schema declared.
No examples provided.
supplier_list List suppliers ~97
List the supplier directory A to Z by name: contact, payment terms, lead time, when each record was last reviewed and how many days ago that was. Filter by category and by free text across every field. Reads only.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Only suppliers in exactly this category, case-insensitive |
| q | string | – | Only suppliers whose name, category, contact, terms or notes contain this text, case-insensitive |
No output schema declared.
No examples provided.
supplier_mark_reviewed Stamp a supplier as reviewed ~111
Stamp a supplier's record as reviewed on a date, today by default: you have checked the contact, the terms and the lead time are still true. This is the stamp supplier_due_review reads, so a reviewed record stops being flagged as stale.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | The date you reviewed the record, YYYY-MM-DD. Default today |
| supplier | string | yes | The supplier id, e.g. SUP-2026-0003, or the name when only one supplier has it |
No output schema declared.
No examples provided.
supplier_remove Remove a supplier ~83
Remove a supplier from the directory by SUP number or name, returning the record as it stood so nothing is lost silently. The SUP number is never reissued. On the free tier the slot is freed for another supplier.
| Name | Type | Req | Description |
|---|---|---|---|
| supplier | string | yes | The supplier id, e.g. SUP-2026-0003, or the name when only one supplier has it |
No output schema declared.
No examples provided.
supplier_update Change a supplier record ~278
Change any of a supplier's fields by SUP number or name: name, category, the contact fields, payment terms, lead time, notes. Only the fields you pass change; pass at least one. The SUP number and the review stamp are not writable here -- supplier_mark_reviewed does the stamp.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Postal or visiting address |
| category | string | – | What they supply, e.g. Packaging, Raw materials, Print. Free-form; supplier_list filters on it |
| contact_name | string | – | Your person there, e.g. Maria Chen |
| string | – | Orders or accounts email | |
| lead_time_days | integer | – | Typical days from order to delivery, e.g. 14 |
| name | string | – | Rename the supplier |
| notes | string | – | Anything worth remembering: minimum orders, who to escalate to, why you dropped them last time |
| payment_terms | string | – | The terms you buy on, e.g. Net 30, 50% upfront, Due on receipt |
| phone | string | – | Phone number as you would dial it |
| supplier | string | yes | The supplier id, e.g. SUP-2026-0003, or the name when only one supplier has it |
| website | string | – | Website or storefront URL |
No output schema declared.
No examples provided.
What is the io.github.theluckystrike/supplier-list MCP server?
io.github.theluckystrike/supplier-list is an MCP server listed in the public MCP registry as io.github.theluckystrike/supplier-list. A supplier directory that does not rot: contacts, terms, lead times, review dates. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/supplier-list.mcpb).
Is the io.github.theluckystrike/supplier-list MCP server safe to use?
io.github.theluckystrike/supplier-list scores 47 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-list MCP server expose?
io.github.theluckystrike/supplier-list exposes 10 tools: supplier_add, supplier_list, supplier_get, supplier_update, supplier_remove, and 5 more. Their descriptions and schemas cost roughly 1,244 tokens of context every time the server is loaded.
What licence is the io.github.theluckystrike/supplier-list MCP server under?
io.github.theluckystrike/supplier-list declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.