Website Feedback Tool MCP server

• Registry nametools.websitefeedback/website-feedback-toolverified in the MCP registry

The registry name sits under websitefeedback.tools. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-27
• Tools5
• Server calls itselfwebsite-feedback-tool
• Server version0.1.2
• Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 1354 ms.

• Its tools do none of the product's use cases we checked: pin comments and screenshots onto live web pages; share one review link with teammates in context.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• What an agent can do with it0 of 2 use cases
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer1629 ms
• Space in an agent's context≈ 535 tokensthe definitions of all its tools (5), which an agent carries on every turn
• Tool definitionsB · 83 of 100
• Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once

• Not saying whether it only reads or can destroy: 5 of 5

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• list_reviews

  List your recent design reviews pushed from the Design Review browser extension (newest first): website, title, time, comment count and the reviewId to pass to get_review. Use this to pick which review to apply.

• get_latest_review

  Get the most recent design review as Markdown feedback (comments, selectors, computed styles, console/network errors, screenshot URLs).

• get_review

  Get one design review by id as Markdown feedback. Obtain the id from list_reviews.

• open_review_link

  Open a design review from a share link somebody sent you (a /r/<id>?t=… URL) and get its feedback as Markdown. Use this when the user pastes a review link rather than asking for their own reviews — the link carries its own access, so the…

• get_screenshot

  View a comment's screenshot inline (clients don't fetch image URLs themselves). Pass the reviewId and the comment id shown next to the screenshot in get_review.