Skip to content

McpStamp Supplier List MCP server

io.github.theluckystrike/supplier-listtheluckystrikestreamable-httpv0.23.0Scanned

A supplier directory: contacts, payment terms, lead times, review dates and CSV export.

10 tools: 1 can delete or cancel things, 6 change things and 3 only read.

Tools: 1 delete, 0 irreversible, 6 write, 3 read.
  • Reads private data · 2
  • Reads text others write · 1
  • Can send data out · 2
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the McpStamp Supplier List MCP server can do

The McpStamp Supplier List MCP server is published by the GitHub account theluckystrike. It has 10 tools. It can delete or cancel things (1 tool: supplier_remove) and create or change data (6 tools: supplier_add, supplier_update, supplier_mark_reviewed, supplier_due_review and 2 more). 3 tools only read.

2 tools read private data (supplier_list and supplier_get); 1 tool brings in text other people can write (license_status); 2 tools can send data out of your system (supplier_add and supplier_update). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 0.23.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

10 tools

Deletes or cancels 1Claude Code: deny
  • supplier_removeRemove a supplier from the directory by SUP number or name, returning the record as it stood so nothing is lost silently.No findings

    Why it is in this group

    • The name "supplier_remove" says "remove": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
Changes things 6Claude Code: ask
  • license_activateTurn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • supplier_addAdd 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.Can send data outNo findings

    Why it is in this group

    • The name "supplier_add" says "add": a word for a change.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • supplier_due_reviewThe due-review report: every supplier whose record has not been reviewed in the last N days -- 90 unless you say otherwise -- most overdue first.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • supplier_exportExport the supplier directory as CSV or a Markdown table: every field, one row per supplier, A to Z by name.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • supplier_mark_reviewedStamp 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.No findings

    Why it is in this group

    • The name "supplier_mark_reviewed" says "mark": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • supplier_updateChange any of a supplier's fields by SUP number or name: name, category, the contact fields, payment terms, lead time, notes.Can send data outNo findings

    Why it is in this group

    • The name "supplier_update" says "update": a word for a change.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • license_statusReport 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.Reads text others writeNo findings

    Why it is in this group

    • The name "license_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • supplier_getRead 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 private dataNo findings

    Why it is in this group

    • The name "supplier_get" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "contact": it reads contacts.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • supplier_listList 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.Reads private dataNo findings

    Why it is in this group

    • The name "supplier_list" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "directory": it reads files.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

4 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 untrusted-input tool breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__supplier-list__license_status"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:35 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
7
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/supplier-list
Authorization servers
https://mcp.zovo.one
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (1 destructive, 6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.zovo.one/mcp/supplier-list: tools/list returned 10 tools to an anonymous client, including supplier_remove (destructive), supplier_add (write), supplier_update (write), supplier_mark_reviewed (write), supplier_due_review (write) and 2 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • HTTP status of an anonymous initialize: 429 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 7
    • Protocol version: none to 2025-06-18
  2. Nov 6, 2026
    • RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource to https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/supplier-list
  3. Oct 29, 2026
    • HTTP status of an anonymous initialize: 200 to 429
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 7 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 429 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 7 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 429 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 7
    • Protocol version: none to 2025-06-18
  2. PostureRemote posture changed. RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource -> https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/supplier-list.View diff
    • RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource to https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/supplier-list
  3. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 429; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 7 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 429
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 7 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 0.23.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http supplier-list https://mcp.zovo.one/mcp/supplier-list
claude mcp add --transport http supplier-list https://mcp.zovo.one/mcp/supplier-list

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__supplier-list__supplier_list",
      "mcp__supplier-list__supplier_get",
      "mcp__supplier-list__license_status"
    ],
    "ask": [
      "mcp__supplier-list__supplier_add",
      "mcp__supplier-list__supplier_update",
      "mcp__supplier-list__supplier_mark_reviewed",
      "mcp__supplier-list__supplier_due_review",
      "mcp__supplier-list__supplier_export",
      "mcp__supplier-list__license_activate"
    ],
    "deny": [
      "mcp__supplier-list__supplier_remove"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as supplier-list. Review it before you use it.

Capability tags behind 5 rules
  • mcp__supplier-list__supplier_add outbound
  • mcp__supplier-list__supplier_list private-data
  • mcp__supplier-list__supplier_get private-data
  • mcp__supplier-list__supplier_update outbound
  • mcp__supplier-list__license_status untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.theluckystrike/supplier-list/verify?hash=233d9593cc51defa2d45d2bb2253dcc432d845993aefc226c5ee7bc1e0fdf625" | jq -e '.changed == false'

Pinned hash 233d9593cc51, from Nov 15, 2026, 06:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.theluckystrike/supplier-list/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.theluckystrike/supplier-list
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.theluckystrike/supplier-list.svg)](https://radar.anlyon.com/servers/io.github.theluckystrike/supplier-list)

Source: MCP Registry · repository. Synced Nov 2, 2026, 03:18 UTC.

McpStamp Supplier List MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the McpStamp Supplier List MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the McpStamp Supplier List MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: supplier_remove.

Can the McpStamp Supplier List MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the McpStamp Supplier List MCP server have?

10 tools: 1 destructive, 6 write, 3 read. supplier_remove, supplier_add, supplier_update, supplier_mark_reviewed, supplier_due_review, supplier_export, license_activate, supplier_list and 2 more.

Does the McpStamp Supplier List MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the McpStamp Supplier List MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): supplier_add and supplier_update.

Has the McpStamp Supplier List MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.