peek vs io.github.dynamicupgrade/chromedebug
peek is an MCP server published by Cubenest. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.dynamicupgrade/chromedebug is an MCP server published by dynamicupgrade. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |  peek | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0-alpha.24 Downloads/month (npm): 280 Downloads/week (npm): 51 Forks (GitHub): 0 Stars (GitHub): 8 Not marked · First seen |
Listed Version: 2.9.6 Downloads/month (npm): 1 749 Downloads/week (npm): 87 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 | peek | io.github.dynamicupgrade/chromedebug |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 8 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@peekdev/mcp) | On your machine (@dynamicu/chromedebug-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/cubenest/rrweb-stack | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
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
peek
Exposes recorded browser sessions (rrweb DOM, console, network) to AI coding agents, fully local
io.github.dynamicupgrade/chromedebug
Record browser bugs - frames, clicks and console logs - and hand them to your AI over MCP.
How to run each
peek As a local MCP server: npm package
claude mcp add --transport stdio peek-mcp -- npx -y @peekdev/mcpio.github.dynamicupgrade/chromedebug As a local MCP server: npm package
claude mcp add --transport stdio chromedebug -- npx -y @dynamicu/chromedebug-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
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: peek · What it can do: io.github.dynamicupgrade/chromedebug · Compare two other plugins
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.