Supplier Directory MCP Server

by theluckystrike Your server? Claim it

answering

Supplier Directory is answering right now. Last checked 13 min ago. It exposes 10 tools. Last commit 22 Oct 2026.

A supplier directory that does not rot: contacts, payment terms, lead times, due-review report.

Uptime history 32 days of history · worst day 92%

32 days agonow

100.0%

Uptime 24h

87 of 87 checks

Tools

read from the server

252 ms

Response time

average over 24h

Stars

last commit 22 Oct 2026

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 15 October 2026. No other catalogue keeps this.

15 Oct a tool changed version

What the code does

We read the source, 2 d ago · tools taken from the live server · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Hidden recipient in outgoing message billing/src/index.js:1340

        reply_to: "[email protected]" }),

Touches key and credential files data/npm_unblock.json:34

        "confound": "actions/setup-node with registry-url wrote NPM_CONFIG_USERCONFIG=$RUNNER_TEMP/.npmrc containing //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}; with no NODE_AUTH_TOKEN secret this expanded to the literal placeholder XXXXX-XXXXX-XXXXX-XXXXX, so npm authen…

Dumps the whole environment servers/office-suite/src/index.ts:141

  for (const [k, v] of Object.entries(process.env)) if (v !== undefined) env[k] = v;

Page loads a third-party script telegram/public/index.html:11

<script src="https://telegram.org/js/telegram-web-app.js"></script>

Sends data to a third-party sink telegram/src/bot.ts:205

  console.error("Bot started; polling https://api.telegram.org");

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://mcp.zovo.one/mcp/supplier-directory

~/.codex/config.toml

[mcp_servers.supplier-directory]
url = "https://mcp.zovo.one/mcp/supplier-directory"

.cursor/mcp.json

{
  "mcpServers": {
    "supplier-directory": {
      "url": "https://mcp.zovo.one/mcp/supplier-directory"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "supplier-directory": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/supplier-directory"
    }
  }
}

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

supplier

supplier_add

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.

supplier_due_review

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.

supplier_export

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.

supplier_get

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.

supplier_list

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.

supplier_mark_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.

supplier_remove

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.

supplier_update

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.

license

license_activate

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.

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.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.zovo.one/mcp/supplier-directory	streamable-http	answering	457 ms	13 min ago

Alternatives to Supplier Directory

same job, measured the same way

NotWorking

by notworking

Downdetector for AI agents: stop paying for retries that can't succeed. Check once, then report.

2 tools answering

Xero

by mindstone

Xero MCP server for invoices, contacts, payments, quotes, and financial reports.

25 installs/wk local only

Asking

by com-asking

Asking support MCP: read conversations, contacts and reports, and reply with scoped consent.

answering

MCP Xero

by codespar

MCP server for Xero — global cloud accounting: contacts, invoices, payments, items, reports

14 installs/wk local only

Xero

by wyre-technology

MCP server for Xero accounting — contacts, invoices, payments, accounts, and financial reports.

local only

Xero

by wyre-ai

MCP server for Xero accounting — contacts, invoices, payments, accounts, and financial reports.

local only

MCP Link In Bio Newsletter Checker

by mambabuilt

Follow a creator bio link and report the newsletter, what they sell, and the contact emails.

228 installs/wk local only

FeedbackThread

by feedbackthread

Triage app feedback and store reviews, draft replies and release notes, tell reporters what shipped.

answering

Supplier Directory — questions

Answers built from our own checks of this server.

What can Supplier Directory do?

It exposes 10 tools, read directly from the server on our last check. Among them: license_activate, license_status, supplier_add, supplier_due_review, supplier_export, supplier_get and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Supplier Directory mostly used for?

Its tools cluster around supplier and license. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Supplier Directory working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 87 of 87 checks got a reply (100.0%), average response time 252 ms. The bar chart above shows every period we have measured.

How do I connect Supplier Directory?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Supplier Directory need an API key?

No. Supplier Directory completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Supplier Directory?

It answers our handshake in 252 ms on average, which is faster than 59% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Supplier Directory open source?

The code is open source: it is published under the MIT licence, written in JavaScript and 2 stars on GitHub. The licence covers the code in the repository, not the hosted service at mcp.zovo.one, which runs on its operator's own terms.