# io.github.theluckystrike/supplier-list (remote · mcp.zovo.one)

A supplier directory that does not rot: contacts, terms, lead times, review dates.

- Trust score: 81/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `mcp.zovo.one`: 81/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-supplier-list/mcp-supplier-list.md), [page](https://verifymcp.io/servers/theluckystrike-supplier-list/mcp-supplier-list)
- mcpb · `supplier-list.mcpb`: 47/100, [markdown](https://verifymcp.io/servers/theluckystrike-supplier-list/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-supplier-l.md), [page](https://verifymcp.io/servers/theluckystrike-supplier-list/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-supplier-l)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/supplier-list`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-09-21.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 87/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1301 tokens (~118/item across 11 items; 10 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 11 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-list MCP server?

io.github.theluckystrike/supplier-list is a hosted endpoint at https://mcp.zovo.one/mcp/supplier-list, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http theluckystrike-supplier-list 'https://mcp.zovo.one/mcp/supplier-list'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-supplier-list": {
      "url": "https://mcp.zovo.one/mcp/supplier-list"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-supplier-list": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/supplier-list"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-supplier-list]
url = "https://mcp.zovo.one/mcp/supplier-list"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-supplier-list": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/supplier-list",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-supplier-list --url 'https://mcp.zovo.one/mcp/supplier-list' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-supplier-list:
    url: "https://mcp.zovo.one/mcp/supplier-list"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-supplier-list": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/supplier-list"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-supplier-list -t streamable-http -u 'https://mcp.zovo.one/mcp/supplier-list'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-supplier-list": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/supplier-list"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-09-21 (score 81, +2)

- [security] Tool “supplier_remove” is now declared destructive
- [functional] Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.

### 2026-09-19 (score 79, +1)

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

### 2026-09-18 (score 78, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-17 (score 78)

First indexed and scored.

## MCP tools (10)

### `supplier_add` (~260 tokens)

Add a supplier

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.

Input parameters:

- `address` (string): Postal or visiting address
- `category` (string, required): 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
- `email` (string): Orders or accounts email
- `lead_time_days` (integer): Typical days from order to delivery, e.g. 14
- `name` (string, required): 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

### `supplier_list` (~97 tokens)

List suppliers

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.

Input parameters:

- `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

### `supplier_get` (~77 tokens)

Read one supplier

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.

Input parameters:

- `supplier` (string, required): The supplier id, e.g. SUP-2026-0003, or the name when only one supplier has it

### `supplier_update` (~278 tokens)

Change a supplier record

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.

Input parameters:

- `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
- `email` (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, required): The supplier id, e.g. SUP-2026-0003, or the name when only one supplier has it
- `website` (string): Website or storefront URL

### `supplier_remove` (~83 tokens)

Remove a supplier

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.

Input parameters:

- `supplier` (string, required): The supplier id, e.g. SUP-2026-0003, or the name when only one supplier has it

### `supplier_mark_reviewed` (~111 tokens)

Stamp a supplier as reviewed

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.

Input parameters:

- `date` (string): The date you reviewed the record, YYYY-MM-DD. Default today
- `supplier` (string, required): The supplier id, e.g. SUP-2026-0003, or the name when only one supplier has it

### `supplier_due_review` (~91 tokens)

Which supplier records have gone stale

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.

Input parameters:

- `days` (integer): A record is due when its last review is older than this many days. Default 90

### `supplier_export` (~122 tokens)

Export the directory

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.

Input parameters:

- `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

### `license_status` (~55 tokens)

License status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

### `license_activate` (~76 tokens)

Activate license

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-supplier-list/mcp-supplier-list#diagnostics

## Score history

- 2026-09-21: 81
- 2026-09-20: 79
- 2026-09-19: 79
- 2026-09-18: 78
- 2026-09-17: 78

## Common questions

### 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 hosted endpoint (https://mcp.zovo.one/mcp/supplier-list).

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

io.github.theluckystrike/supplier-list scores 81 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 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,250 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/supplier-list MCP server require authentication?

Yes. io.github.theluckystrike/supplier-list asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.github.theluckystrike/supplier-list MCP server still maintained?

io.github.theluckystrike/supplier-list is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/supplier-list
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/supplier-list
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/supplier-list
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-supplier-list/mcp-supplier-list.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-supplier-list/mcp-supplier-list.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-supplier-list/mcp-supplier-list