VendorWatch MCP Server

by sergiomaldo Your server? Claim it

not responding

VendorWatch is listed as active in the registry but did not answer our last check. It exposes 4 tools.

Check a vendor before you sign: DPA coverage, subprocessors, certifications, data locations, AI use.

Uptime history 33 days of history · worst day 0%

33 days agonow

0.0%

Uptime 24h

0 of 92 checks

Tools

read from the server

80 ms

Response time

average over 24h

open, no key

Access

streamable-http

VendorWatch does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add vendorwatch --transport http https://vendor.watch/api/v1/mcp

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

https://vendor.watch/api/v1/mcp

~/.codex/config.toml

[mcp_servers.vendorwatch]
url = "https://vendor.watch/api/v1/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "vendorwatch": {
      "url": "https://vendor.watch/api/v1/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "vendorwatch": {
      "type": "http",
      "url": "https://vendor.watch/api/v1/mcp"
    }
  }
}

Available tools 4

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

vendor

find_vendor

Find a vendor in the VendorWatch catalogue by its exact name or website domain. Returns up to 5 candidates (slug, name, category). Free: no lookup is spent.

get_vendor_profile

Get one vendor's documentation profile: DPA coverage by law, number of subprocessors, certifications, data locations, transfer safeguards and AI use. Give the slug from find_vendor, or the vendor's name or domain. Spends one lookup.

list_vendor_changes_since

List the vendors in your VendorWatch portfolio whose record changed on or after a date (profile updated, DPA analysed, DPA document changed). Free: no lookup is spent. 50 vendors a page; read the new profile with get_vendor_profile.

portfolio

check_portfolio

Check a list of up to 25 vendors (names, domains or both) and get one profile each. Spends one lookup per vendor answered; a name that matches nothing costs nothing.

Endpoints

URL	Transport	State	Latency	Checked
https://vendor.watch/api/v1/mcp	streamable-http	answering	80 ms	0 min ago

Alternatives to VendorWatch

same job, measured the same way

SSL Certificate Check

by powmcp

Inspect one endpoint's served certificate, expiry, hostname coverage, and accepted TLS versions.

1 tools answering

Conarium

by dogrucanemek-alt

Governed database access for AI assistants: masking, signed receipts, coverage reconciliation.

784 installs/wk local only

Open Waters AIS

by openwaters

Live AIS vessel positions by MMSI, name, area, or radius, plus coverage. No sign-in, no key.

6 tools answering

Facesign MCP

by facesign

Build and test FaceSign step-up verification flows from your AI coding tool

5 tools answering

Uxloom

by uxloom-dev

Agent-native UI/UX design validation: journey completeness, state coverage, and WCAG checks.

88 installs/wk local only

Free100LocalLeads

by free100localleads

Check local business contact coverage by country, category and US state.

answering

Catalog QA Desk

by openkrill

Check an online store's product catalog before you import it or send it to a shopping feed.

7 tools answering

Verzi Health

by verzi

Medicare DME coverage by HCPCS code and date of service, with CMS citations and signed receipts.

6 tools answering

VendorWatch — questions

Answers built from our own checks of this server.

What can VendorWatch do?

It exposes 4 tools, read directly from the server on our last check. Among them: check_portfolio, find_vendor, get_vendor_profile, list_vendor_changes_since. 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 →

Is VendorWatch working right now?

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

The registry lists VendorWatch as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect VendorWatch?

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 VendorWatch need an API key?

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