McpStamp Supplier List
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS
A supplier directory: contacts, payment terms, lead times, review dates and CSV export.
Available components
Last scanned (22 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 4 Nov 2026.
Category CRM and Sales
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. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1384 tokens (~125/item across 11 items; 10 tools + 1 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 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 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 12 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.
- 2 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 26 +1
- Server version: 0.22.0 → 0.22.6 functional
- 15 Oct 26 +69
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Stability: unverified → 0.93 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 14 Oct 26 −64
- Endpoint reachability: reachable → behind authorisation ▼ security
- Transport: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.57 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
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 · Probed https://mcp.zovo.one/mcp/supplier-list
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 39e1adfa4eb6500e0e3d48868766e3e9 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/supplier-list"
Bearer realm="mcp.zovo.one", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/supplier-list"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Document | https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/supplier-list |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.zovo.one/mcp/supplier-list |
| Authorisation server | https://mcp.zovo.one |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/supplier-list | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/supplier-list | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/supplier-list |
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 ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
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.
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.
How do I install the McpStamp Supplier List MCP server?
McpStamp 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.
remote · mcp.zovo.one
claude mcp add --transport http theluckystrike-supplier-list 'https://mcp.zovo.one/mcp/supplier-list'
What is the McpStamp Supplier List MCP server?
McpStamp Supplier List is an MCP server listed in the public MCP registry as io.github.theluckystrike/supplier-list. A supplier directory: contacts, payment terms, lead times, review dates and CSV export. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/supplier-list).
Is the McpStamp Supplier List MCP server safe to use?
McpStamp Supplier List scores 95 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 McpStamp Supplier List MCP server expose?
McpStamp 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 McpStamp Supplier List MCP server require authentication?
Yes. McpStamp 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 McpStamp Supplier List MCP server still maintained?
McpStamp Supplier List 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.