Perplexity API Platform vs Comprot: Processo
Perplexity API Platform is an MCP server published by perplexity.ai. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, Community GitHub marketplaces). Comprot: Processo is an MCP server published by mcp-dir. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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 API Platform |  Comprot: Processo |
|---|---|---|
| Official MCP Registry | Listed Version: 1.2.1 Downloads/month (npm): 104 497 Downloads/week (npm): 14 694 Not marked · First seen |
Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:7816f45a6f26 Forks (GitHub): 380 Pulls (Docker Hub): 79 944 Stars (Docker Hub): 17 Stars (GitHub): 2 563 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 | Perplexity API Platform | Comprot: Processo |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 2 563 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 79 944 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 380 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@perplexity-ai/mcp-server) | Remote server (api.mcp.ai/p_comprot_processo) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/ppl-ai/modelcontextprotocol | github.com/mcp-dir/comprot_processo-mcp |
| Changes in the last 7 days (differs) | 3 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 35 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 API Platform
Real-time web search, reasoning, and research through Perplexity's API
Comprot: Processo
Comprot: Court Case, official-source lookup. Platform-hosted, pay per query with prepaid credit.
How to run each
Perplexity API Platform As a local MCP server: npm package
claude mcp add --transport stdio perplexity-api-platform -- npx -y @perplexity-ai/mcp-serverComprot: Processo As a remote MCP server
claude mcp add --transport http comprot-processo-mcp https://api.mcp.ai/p_comprot_processoCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Comprot: Processo has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Comprot: Processo publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Comprot: Processo publish no settings it asks for, so we do not compare settings.
What it can do: Perplexity API Platform · What it can do: Comprot: Processo · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.