# VendorWatch (remote · vendor.watch)

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

- Trust score: 88/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `vendor.watch`: 88/100 (this document), [markdown](https://verifymcp.io/servers/sergiomaldo-vendorwatch/api-v1-mcp.md), [page](https://verifymcp.io/servers/sergiomaldo-vendorwatch/api-v1-mcp)

## Channel facts

- Endpoint: `https://vendor.watch/api/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 389 tokens (~97/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the VendorWatch MCP server?

VendorWatch is a hosted endpoint at https://vendor.watch/api/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http sergiomaldo-vendorwatch 'https://vendor.watch/api/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "sergiomaldo-vendorwatch": {
      "url": "https://vendor.watch/api/v1/mcp"
    }
  }
}
```

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sergiomaldo-vendorwatch": {
      "type": "remote",
      "url": "https://vendor.watch/api/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sergiomaldo-vendorwatch --url 'https://vendor.watch/api/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  sergiomaldo-vendorwatch:
    url: "https://vendor.watch/api/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "sergiomaldo-vendorwatch": {
      "Transport": "http",
      "Url": "https://vendor.watch/api/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add sergiomaldo-vendorwatch -t streamable-http -u 'https://vendor.watch/api/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "sergiomaldo-vendorwatch": {
      "type": "http",
      "url": "https://vendor.watch/api/v1/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `find_vendor` (~91 tokens)

Find a 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.

Input parameters:

- `domain` (string): The vendor's website domain, or any host under it (for example app.example.com).
- `name` (string): The vendor's name, written in full (for example the name on its website).

### `get_vendor_profile` (~124 tokens)

Get a vendor's 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.

Input parameters:

- `domain` (string): The vendor's website domain, or any host under it (for example app.example.com).
- `name` (string): The vendor's name, written in full (for example the name on its website).
- `slug` (string): The vendor's VendorWatch identifier, as returned by find_vendor.

### `list_vendor_changes_since` (~105 tokens)

List changes since a date

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.

Input parameters:

- `cursor` (string): The `next` value from the previous page, to read the following page.
- `since` (string, required): A date, YYYY-MM-DD. Changes on or after this date are listed.

### `check_portfolio` (~69 tokens)

Check a list of vendors

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.

Input parameters:

- `vendors` (array, required): Up to 25 vendors, each with a name, a domain or both.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/sergiomaldo-vendorwatch/api-v1-mcp#diagnostics

## Score history

- 2026-11-04: 88
- 2026-11-03: 87
- 2026-11-02: 87
- 2026-11-01: 86
- 2026-10-31: 86
- 2026-10-30: 85
- 2026-10-29: 85
- 2026-10-28: 84
- 2026-10-27: 84
- 2026-10-26: 83
- 2026-10-25: 83
- 2026-10-24: 83
- 2026-10-23: 82
- 2026-10-22: 82
- 2026-10-21: 81
- 2026-10-20: 81
- 2026-10-19: 80
- 2026-10-18: 80
- 2026-10-17: 79
- 2026-10-16: 79
- 2026-10-15: 78
- 2026-10-14: 78
- 2026-10-13: 77
- 2026-10-12: 77
- 2026-10-10: 76
- 2026-10-08: 75

## Common questions

### What is the VendorWatch MCP server?

VendorWatch is an MCP server listed in the public MCP registry as io.github.sergiomaldo/vendorwatch. Check a vendor before you sign: DPA coverage, subprocessors, certifications, data locations, AI use. This page covers its hosted endpoint (https://vendor.watch/api/v1/mcp).

### Is the VendorWatch MCP server safe to use?

VendorWatch scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the VendorWatch MCP server expose?

VendorWatch exposes 4 tools: find_vendor, get_vendor_profile, list_vendor_changes_since, check_portfolio. Their descriptions and schemas cost roughly 389 tokens of context every time the server is loaded.

### Does the VendorWatch MCP server require authentication?

No. We connected to VendorWatch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the VendorWatch MCP server still maintained?

VendorWatch is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://vendor.watch/api/v1/mcp
- Authorisation metadata: https://vendor.watch/.well-known/oauth-protected-resource/api/v1/mcp
- Website: https://vendor.watch/agents
- Changelog RSS feed: https://verifymcp.io/servers/sergiomaldo-vendorwatch/api-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/sergiomaldo-vendorwatch/api-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/sergiomaldo-vendorwatch/api-v1-mcp