Security & Testing
vendor.watch
A VendorWatch MCP server that looks up vendor privacy/security profiles and monitors portfolio changes for DPA coverage, subprocessors, certifications, data locations, transfer safeguards, and AI use.
ENDPOINT 1
https://vendor.watch/api/v1/mcp
MCP server metadata
- Name
- vendorwatch
- Version
- 1.0.0
Known tools 4
find_vendorFind a vendor in the VendorWatch catalogue by its exact name or website domain.
Inferred read-onlyget_vendor_profileGet one vendor's documentation profile: DPA coverage by law, number of subprocessors, certifications, data locations, transfer safeguards and AI use.
Potential side effectslist_vendor_changes_sinceList the vendors in your VendorWatch portfolio whose record changed on or after a date (profile updated, DPA analysed, DPA document changed).
Inferred read-onlycheck_portfolioCheck a list of up to 25 vendors (names, domains or both) and get one profile each.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.vendorwatch]
url = "https://vendor.watch/api/v1/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"vendorwatch": {
"type": "http",
"url": "https://vendor.watch/api/v1/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: vendorwatch
Remote MCP URL: https://vendor.watch/api/v1/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"vendorwatch": {
"url": "https://vendor.watch/api/v1/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"vendorwatch": {
"type": "http",
"url": "https://vendor.watch/api/v1/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "vendorwatch",
"transport": "streamable-http",
"url": "https://vendor.watch/api/v1/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.