io.github.microsoft/playwright-mcp vs YoPingMe uptime monitoring
io.github.microsoft/playwright-mcp is an MCP server published by microsoft. Marketplaces we read that list it: 4 (Official MCP Registry, Claude Code: claude-plugins-official, Cursor: cursor/plugins, Docker MCP Catalog). YoPingMe uptime monitoring is an MCP server published by yoping.me. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 |  io.github.microsoft/playwright-mcp |  YoPingMe uptime monitoring |
|---|---|---|
| Official MCP Registry | Listed Version: 0.0.82 Downloads/month (npm): 31 345 222 Downloads/week (npm): 6 403 349 Forks (GitHub): 3 283 Stars (GitHub): 38 368 Not marked · First seen |
Listed Version: 1.0.0 No figure published Not marked · First seen |
| Claude Code: claude-plugins-official | Listed Version: not stated Forks (GitHub): 4 580 Stars (GitHub): 43 312 Not marked · First seen |
Not listed |
| Cursor: cursor/plugins | Listed Version: 1.0.0 Forks (GitHub): 1 299 Stars (GitHub): 13 179 Not marked · First seen |
Not listed |
| Docker MCP Catalog | Listed Version: sha256:8771dc4666e7 Forks (GitHub): 3 283 Pulls (Docker Hub): 2 531 203 Stars (Docker Hub): 38 Stars (GitHub): 38 368 Not marked · First seen |
Not listed |
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 | io.github.microsoft/playwright-mcp | YoPingMe uptime monitoring |
|---|---|---|
| Marketplaces that list it (differs) | 4 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 43 312 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 2 531 203 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 4 580 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@playwright/mcp) | Remote server (app.yoping.me/api/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 23 | 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/microsoft/playwright-mcp | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days ago, requires a key |
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
io.github.microsoft/playwright-mcp
Playwright Tools for MCP
YoPingMe uptime monitoring
Website uptime monitoring: live status, uptime reports, incidents, response times, failed checks
How to run each
io.github.microsoft/playwright-mcp As a local MCP server: npm package
claude mcp add --transport stdio playwright-mcp -- npx -y @playwright/mcpYoPingMe uptime monitoring As a remote MCP server
claude mcp add --transport http uptime https://app.yoping.me/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only YoPingMe uptime monitoring has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of YoPingMe uptime monitoring publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: io.github.microsoft/playwright-mcp · What it can do: YoPingMe uptime monitoring · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-plugin/marketplace.json. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.