visual-eyes vs Website Feedback Tool
visual-eyes is a plugin bundle for AI coding tools published by nikolasdehor. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Website Feedback Tool is an MCP server published by websitefeedback.tools. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  visual-eyes | |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 3 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.2 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | visual-eyes | Website Feedback Tool |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 3 | No figure on GitHub |
| Forks (GitHub) (differs) | 3 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (dfozgzaflbudvthtlhvn.supabase.co/functions/v1/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/nikolasdehor/visual-eyes | Not stated |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-12 | 2026-10-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 12 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
visual-eyes
Give Claude Code the ability to see running web applications. Visual Eyes captures screenshots via Playwright, lets Claude analyze the UI visually, auto-fix layout bugs, and run pixel-level regression testing. Works with any localhost app, zero config needed. Supports desktop, mobile, and full-page captures.
Website Feedback Tool
Read visual design reviews from live web pages: comments, CSS selectors, styles, console errors.
How to run each
visual-eyes As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install visual-eyes@claude-communityWebsite Feedback Tool As a remote MCP server
claude mcp add --transport http website-feedback-tool https://dfozgzaflbudvthtlhvn.supabase.co/functions/v1/mcp --header "Authorization: Bearer <YOUR_AGENT_KEY>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Website Feedback Tool has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: visual-eyes · What it can do: Website Feedback Tool · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.