MCP.Market

VendorWatch MCP server

online · 100% uptime
by sergiomaldo·io.github.sergiomaldo/vendorwatch·v1.0.0
No reviews yet

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

C64/100grade C
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
C64/100

full report

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed VendorWatch yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

VendorWatch tools (4)

write = sends, deletes, buys or posts
  • check_portfolioFree

    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.

  • find_vendorFree

    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_profileFree

    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_sinceFree

    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.

Public scan report

scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it

1 low
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1671ms20/20
  • Tool poisoning4 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenanceno repository listed3/15
  • Maintainer identityno repository or website to verify2/10

Findings (1)

  • lowNo source repository listedmaint.no-repo
Overall 64/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How VendorWatch compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
64/100
higher than 19% of 48,255 servers
Tools
4
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
301 ms
faster than 48% of 30,031 servers

What its tools let an agent do: 4 read

Install VendorWatch in Claude Code, Cursor or VS Code

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

VendorWatch: common questions

Is VendorWatch MCP server safe?
With care: it is graded C, so read the findings first (64/100). Read the VendorWatch safety report
How do I install VendorWatch?
It runs remotely at vendor.watch. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does VendorWatch need an API key?
Yes. The registry entry asks for Authorization.
Is VendorWatch maintained?
The latest release is v1.0.0.
Is VendorWatch up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does VendorWatch compare with other MCP servers?
safety score 64/100 (higher than 19% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.