upAPI vs PrismSearch
upAPI is an MCP server published by DevinoSolutions. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). PrismSearch is an MCP server published by xiaonerner0821. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. 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 |   upAPI |  PrismSearch |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.0 Downloads/month (npm): 990 Downloads/week (npm): 196 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.3.3 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 0.2.0 Downloads/month (npm): 990 Downloads/week (npm): 196 Forks (GitHub): 0 Stars (GitHub): 0 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 | upAPI | PrismSearch |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-11-02 |
| Where it runs (differs) | Remote server or your machine | On your machine (prismsearch) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 5, secrets among them: 2 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/devinosolutions/upapi-mcp | github.com/xiaonerner0821/prismsearch |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-29 |
| Endpoint at the last check (differs) | Responded 8 h ago, requires authentication | no remote endpoint we check |
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
upAPI
All public upAPI operations as MCP tools: web scraping, search, screenshots, PDF, OCR and more.
PrismSearch
Multi-engine web, image and WeChat search with page/PDF fetching over local MCP stdio.
How to run each
upAPI As a remote MCP server
claude mcp add --transport http upapi-mcp https://app.upapi.io/api/mcpRequires: UPAPI_API_KEY (secret)
PrismSearch As a local MCP server: npm package
claude mcp add --env "BRAVE_API_KEY=<YOUR_BRAVE_API_KEY>" --env "GOOGLE_API_KEY=<YOUR_GOOGLE_API_KEY>" --transport stdio prismsearch -- npx -y prismsearchRequires: BRAVE_API_KEY (secret), GOOGLE_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only upAPI 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
Only upAPI asks for
UPAPI_API_KEY (secret)UPAPI_TOOL_MODE
Only PrismSearch asks for
BRAVE_API_KEY (secret)GOOGLE_API_KEY (secret)GOOGLE_CSE_IDPRISMSEARCH_CONFIGPRISMSEARCH_HOME
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: upAPI · What it can do: PrismSearch · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.