Skip to content

watch.diy – DIY Store Finder MCP server

diy.watch/diy-store-finderwatch.diystreamable-httpv1.0.0Scanned

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

2 tools: 1 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 1 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the watch.diy – DIY Store Finder MCP server can do

The watch.diy – DIY Store Finder MCP server is published by watch.diy, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: where_to_buy_nearby), but cannot delete data. 1 tool only reads.

1 tool brings in text other people can write (where_to_buy_nearby).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 14, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Changes things 1Claude Code: ask
  • where_to_buy_nearbyChecks 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 …Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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), 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.

    Annotations the server declares

    • title: Check availability at stores near a postcode
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • find_productSearches 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 …No findings

    Why it is in this group

    • The name "find_product" says "find": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find a product and its prices per chain
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:21 UTC, unchanged since Nov 21, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.watch.diy/public/mcp: tools/list returned 2 tools to an anonymous client, including where_to_buy_nearby (write)

    What this check looks for

Posture changes

  1. Nov 21, 2026
    • RFC 9728 protected resource metadata: https://mcp.watch.diy/.well-known/oauth-protected-resource to none
    • Authorization servers: https://mcp.watch.diy to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. RFC 9728 protected resource metadata: https://mcp.watch.diy/.well-known/oauth-protected-resource -> none; Authorization servers: https://mcp.watch.diy -> none; Dynamic client registration: yes -> not observed (and 1 …View diff
    • RFC 9728 protected resource metadata: https://mcp.watch.diy/.well-known/oauth-protected-resource to none
    • Authorization servers: https://mcp.watch.diy to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http diy-store-finder https://mcp.watch.diy/public/mcp
claude mcp add --transport http diy-store-finder https://mcp.watch.diy/public/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__diy-store-finder__find_product"
    ],
    "ask": [
      "mcp__diy-store-finder__where_to_buy_nearby"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as diy-store-finder. Review it before you use it.

Capability tags behind 1 rule
  • mcp__diy-store-finder__where_to_buy_nearby untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/diy.watch/diy-store-finder/verify?hash=e3848a61ac83b29658ab663a44e3f7b7544e99b235c5885d90879dd7b6b11e8d" | jq -e '.changed == false'

Pinned hash e3848a61ac83, from Nov 14, 2026, 08:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/diy.watch/diy-store-finder/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for diy.watch/diy-store-finder
[![Anlyon Radar](https://radar.anlyon.com/badge/diy.watch/diy-store-finder.svg)](https://radar.anlyon.com/servers/diy.watch/diy-store-finder)

Source: MCP Registry. Synced Nov 14, 2026, 08:17 UTC.

watch.diy – DIY Store Finder MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

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

No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the watch.diy – DIY Store Finder MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the watch.diy – DIY Store Finder MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the watch.diy – DIY Store Finder MCP server have?

2 tools: 1 write, 1 read. where_to_buy_nearby and find_product.

Does the watch.diy – DIY Store Finder MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the watch.diy – DIY Store Finder MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the watch.diy – DIY Store Finder MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.