Modelcontextprotocol · @modelcontextprotocol vs Perplexity API Platform
Modelcontextprotocol · @modelcontextprotocol scores 8 points higher — a narrow lead. Read the evidence rows below before treating it as decisive. Both are measured the same way, on the same day, from public evidence only — so this is a comparison of two measurements rather than two marketing pages. How we measure ›
| Modelcontextprotocol · @modelcontextprotocol | Perplexity API Platform | what it means | |
|---|---|---|---|
| tashan score | 84 | 76 | upkeep + freshness, gated by adoption |
| Adoption evidence | 551k/wk | 17k/wk | the raw public signal the score came from |
| Last release | active | active | npm publish or repo push |
| Upkeep | 91 | 93 | cadence, maintainers, status |
| Expertise grade | not graded | solid | an LLM read of its own documentation against a fixed rubric |
| Security audit | no known advisories, no build provenance | no known advisories | a summary — the full audit, free, is on each dossier |
| Licence | — | MIT | |
| Maintainers | more than one | more than one | bus-factor risk |
Install either
Modelcontextprotocol · @modelcontextprotocol
claude mcp add modelcontextprotocol-server -- npx -y @modelcontextprotocol/serverPerplexity API Platform
claude mcp add perplexity-ai-mcp-server -- npx -y @perplexity-ai/mcp-serverNeither score is a security verdict — "well maintained" and "nothing known is wrong" are different claims, which is why the audit is a separate row and never folded into the number. The full audit for each — the advisory ids, the version that fixes them and anything that runs at install time — is free on its own page: Modelcontextprotocol · @modelcontextprotocol · Perplexity API Platform.