Perplexity vs 顏回 YanHui Debug AI
Perplexity is an MCP server published by perplexityai. Marketplaces we read that list it: 1 (Docker MCP Catalog). 顏回 YanHui Debug AI is an MCP server published by sstklen. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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 |   Perplexity | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:7816f45a6f26 Forks (GitHub): 380 Pulls (Docker Hub): 79 864 Stars (Docker Hub): 17 Stars (GitHub): 2 562 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.2.0 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 | Perplexity | 顏回 YanHui Debug AI |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 562 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 79 864 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 380 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/perplexity-ask) | Remote server (api.washinmura.jp/mcp/debug/%7Blobster_id%7D) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/ppl-ai/modelcontextprotocol | github.com/sstklen/yanhui-ci |
| 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 | Answered with HTTP 404 (26 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
Perplexity
Connector for Perplexity API, to enable real-time, web-wide research.
顏回 YanHui Debug AI
Debug AI with shared KB. One bug fixed = everyone benefits. KB hit 4ms free, new analysis $0.05.
How to run each
Perplexity As a local MCP server: Docker image
claude mcp add --env "PERPLEXITY_API_KEY=<YOUR_PERPLEXITY_API_KEY>" --transport stdio perplexity-ask -- docker run -i --rm -e PERPLEXITY_API_KEY mcp/perplexity-askRequires: PERPLEXITY_API_KEY (secret)
顏回 YanHui Debug AI
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only 顏回 YanHui Debug AI has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of 顏回 YanHui Debug AI publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of 顏回 YanHui Debug AI publish no settings it asks for, so we do not compare settings.
What it can do: Perplexity · What it can do: 顏回 YanHui Debug AI · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.