# watch.diy – DIY Store Finder (remote · mcp.watch.diy)

Product availability and prices at German DIY stores (OBI, Bauhaus, toom, Hornbach…) by postcode

- Trust score: 77/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.watch.diy`: 77/100 (this document), [markdown](https://verifymcp.io/servers/diy-watch-diy-store-finder/public-mcp.md), [page](https://verifymcp.io/servers/diy-watch-diy-store-finder/public-mcp)

## Channel facts

- Endpoint: `https://mcp.watch.diy/public/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-21.

- **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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 74/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 875 tokens (~291/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 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.
  - Supports UI / widget rendering.

## Install

### How do I install the watch.diy – DIY Store Finder MCP server?

watch.diy – DIY Store Finder is a hosted endpoint at https://mcp.watch.diy/public/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 diy-watch-diy-store-finder 'https://mcp.watch.diy/public/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "diy-watch-diy-store-finder": {
      "url": "https://mcp.watch.diy/public/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "diy-watch-diy-store-finder": {
      "type": "http",
      "url": "https://mcp.watch.diy/public/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.diy-watch-diy-store-finder]
url = "https://mcp.watch.diy/public/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "diy-watch-diy-store-finder": {
      "type": "remote",
      "url": "https://mcp.watch.diy/public/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add diy-watch-diy-store-finder --url 'https://mcp.watch.diy/public/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  diy-watch-diy-store-finder:
    url: "https://mcp.watch.diy/public/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "diy-watch-diy-store-finder": {
      "Transport": "http",
      "Url": "https://mcp.watch.diy/public/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add diy-watch-diy-store-finder -t streamable-http -u 'https://mcp.watch.diy/public/mcp'
```

### Other

```json
{
  "mcpServers": {
    "diy-watch-diy-store-finder": {
      "type": "http",
      "url": "https://mcp.watch.diy/public/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-21 (score 77, +1)

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

### 2026-11-20 (score 76, 0)

- [cosmetic] “find_product” reworded the description of “query”

### 2026-11-19 (score 76, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-11-18 (score 75, +1)

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

### 2026-11-16 (score 74, +1)

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

### 2026-11-15 (score 73, 0)

- [security] Tool “where_to_buy_nearby” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03

### 2026-11-14 (score 73)

First indexed and scored.

## MCP tools (2)

### `where_to_buy_nearby` (~460 tokens)

Check availability at stores near a postcode

Checks the availability of 1-3 products (EANs) at every OBI, Bauhaus, toom, Hornbach, hagebau and Globus store within radiusKm (1-30, default 10) of a German postal code, based on the retailers' pages. Returns per product and retailer: status (read; not_listed_in_our_data = watch.diy knows no listing of this product at that retailer, which may still sell it; no_store_in_radius), the retailer's product name, its product page url, price with priceAsOf (a price older than 35 days is returned as null with priceNote), online with onlineAsOf (orderable or not_orderable: whether the retailer sells it online or to order, for the whole retailer and not a store; null when unknown or older than 35 days), and stores [{name, city, zip, km, state, updated}]. Store state is one of available, not_available, not_sold_in_store, unknown: available (the retailer's page shows it as available at that store), not_available (the retailer's page shows it as not available at that store; it does not mean the store never carries it), not_sold_in_store (the retailer does not sell it in that store), unknown (no information for that store). updated is "recently" (within the last 24 hours) or a date (YYYY-MM-DD). Also returns partial (true when there is no information for some stores), location {plz, radiusKm} and a notice. Can take a few seconds. Limits: public lookups are limited per client and per day. Errors: invalid_request (names the field and the reason, e.g. an unknown postal code), quota_exceeded (with the minutes until it can be tried again), public_unavailable.

Input parameters:

- `plz` (string, required): German postal code (PLZ), 5 digits
- `products` (array, required): 1-3 EANs (GTIN barcodes, 8-14 digits), each once
- `radiusKm` (number): Kilometres around the postal code, 1-30 (default 10)

Output parameters:

- `location` (object)
- `notice` (string)
- `partial` (boolean): true = no information for some stores in the radius (state unknown)
- `products` (array)

### `find_product` (~305 tokens)

Find a product and its prices per chain

Searches watch.diy's index of DIY and garden products at German retailers (OBI, Bauhaus, toom, Hornbach, hagebau, Globus and more) by product name, EAN or manufacturer part number (MPN), and returns up to `limit` (1-5, default 3) products, best match first. Per product: name, brand, its EANs and per retailer the retailer's product name, its product page url and price with priceAsOf (when the price was read; a price older than 35 days is returned as null with priceNote). Only products the retailers sell themselves and still list online; store availability is not part of this answer: use where_to_buy_nearby with an EAN from here and a German postcode. Also returns match (ean, identifier, hybrid or text: how the query was answered) and a notice. When nothing matches, products is empty and message says what the index covers. Limits: public lookups are limited per client. Errors: invalid_request (names the field and the reason), quota_exceeded (with the minutes until it can be tried again), public_unavailable.

Input parameters:

- `limit` (integer): Products to return, 1-5 (default 3)
- `query` (string, required): Product name or description (any language, typos tolerated), an EAN (8 or 12-14 digits) or a manufacturer part number (MPN)

Output parameters:

- `match` (string): How the query was answered: ean / identifier (exact), hybrid (full text + semantic), text (full text)
- `message` (string): Present when nothing was found
- `notice` (string)
- `products` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/diy-watch-diy-store-finder/public-mcp#diagnostics

## Score history

- 2026-11-21: 77
- 2026-11-20: 76
- 2026-11-19: 76
- 2026-11-18: 75
- 2026-11-17: 74
- 2026-11-16: 74
- 2026-11-15: 73
- 2026-11-14: 73

## Common questions

### What is the watch.diy – DIY Store Finder MCP server?

watch.diy – DIY Store Finder is an MCP server listed in the public MCP registry as diy.watch/diy-store-finder. Product availability and prices at German DIY stores (OBI, Bauhaus, toom, Hornbach…) by postcode. This page covers its hosted endpoint (https://mcp.watch.diy/public/mcp).

### Is the watch.diy – DIY Store Finder MCP server safe to use?

watch.diy – DIY Store Finder scores 77 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 watch.diy – DIY Store Finder MCP server expose?

watch.diy – DIY Store Finder exposes 2 tools: where_to_buy_nearby, find_product. Their descriptions and schemas cost roughly 765 tokens of context every time the server is loaded.

### Does the watch.diy – DIY Store Finder MCP server require authentication?

No. We connected to watch.diy – DIY Store Finder without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the watch.diy – DIY Store Finder MCP server still maintained?

watch.diy – DIY Store Finder is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the watch.diy – DIY Store Finder MCP server?

VerifyMCP ran 14 checks on watch.diy – DIY Store Finder, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.watch.diy/public/mcp
- Website: https://watch.diy/assistant
- Changelog RSS feed: https://verifymcp.io/servers/diy-watch-diy-store-finder/public-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/diy-watch-diy-store-finder/public-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/diy-watch-diy-store-finder/public-mcp.json
- HTML version of this page: https://verifymcp.io/servers/diy-watch-diy-store-finder/public-mcp
