Field-by-field comparison
Compare the evidence before choosing an MCP.
Each signal stays separate, missing facts remain visible, and the column order follows your selection.
| Evidence field | Perplexity MCPWatchlist candidate | meilisearchMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP Perplexity · Publisher source ↗ | First-party MCP ecosystem:meilisearch · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Jul 30, 2026 Package: Jul 27, 2026 | Repo: Jul 29, 2026 Package: Not documented |
| Popularity evidence | ||
| GitHub stars | 2,442 GitHub stars · checked 2026-08-14T18:46:26.000Z | 194 GitHub stars · checked 2026-08-14T18:46:26.000Z |
| 30-day package downloads | 93,274 30-day package downloads · checked 2026-07-29T17:30:00.000Z | No reliable download data |
| External adoption evidence |
|
|
| Client coverage | ||
| Client coverage details | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | Follow only the publisher source; credential storage, scopes, and revocation remain under review. | The official server uses a configured Meilisearch host and API key. |
| Cost | Publisher plans, API usage, infrastructure, or per-action charges may apply; MCP100 has not published a cost conclusion. | The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply. |
| Permissions | Exact permissions and read/write boundaries have not completed MCP100 review. | Meilisearch API-key permissions determine index and document operations. |
| Data handling | Candidate-specific retention, subprocess, telemetry, and model-data behavior remain review items. | Authorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive search & research information. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | Use a test account, least privilege, read-only controls where available, and explicit approval for mutations. | Write-enabled keys can alter indexes or documents; use search-only keys for investigation. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review. |
| Evidence date | ||
| Editorial review | 2026-07-24 | 2026-07-30 |
| Candidate evidence | 2026-08-14T18:46:26.000Z | 2026-08-14T18:46:26.000Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →