Perplexity vs HasData Google Scholar
Perplexity is an MCP server published by perplexityai. Marketplaces we read that list it: 1 (Docker MCP Catalog). HasData Google Scholar is an MCP server published by hasdata.com. 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 |  HasData Google Scholar |
|---|---|---|
| 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: 1.0.2 Downloads/month (npm): 594 Downloads/week (npm): 47 Forks (GitHub): 0 Stars (GitHub): 10 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 | HasData Google Scholar |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 562 (better) | 10 (worse) |
| Pulls (Docker Hub) (differs) | 79 864 | 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 (mcp/perplexity-ask) | Remote server (mcp.hasdata.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/ppl-ai/modelcontextprotocol | github.com/hasdata/google-scholar-mcp |
| 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 29 h 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
Perplexity
Connector for Perplexity API, to enable real-time, web-wide research.
HasData Google Scholar
Google Scholar search results, citation counts and citation export formats, as structured JSON.
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)
HasData Google Scholar
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: HASDATA_API_KEY (secret), x-api-key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only HasData Google Scholar has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of HasData Google Scholar publish no list of tools, so we do not compare tools.
Settings each asks for
Only Perplexity asks for
PERPLEXITY_API_KEY (secret)
Only HasData Google Scholar asks for
HASDATA_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Perplexity · What it can do: HasData Google Scholar · 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.