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.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldTavily Search MCPWatchlist candidatePerplexity MCPMCP100 Selected
Task fit
Best for
  • Web search, extract, map, and crawl workflows
  • Teams already using Tavily's hosted search APIs
  • Current web search and cited question answering with Perplexity APIs
  • Research workflows that need a focused search/reasoning MCP rather than browser automation
Not ideal for
  • Security-sensitive deployments that require a recently cleared dependency/advisory review
  • Teams that need purely local/offline search
  • Offline or private-network-only workflows
  • Users who want browser control, arbitrary website mutation, or a free unlimited search service
Avoid when
  • You cannot safely manage the API key or OAuth grant
  • Untrusted web content cannot be safely isolated from downstream actions
  • You cannot safely store a Perplexity API key
  • You plan to expose the local HTTP transport publicly without adding inbound authentication and explicit host/origin allowlists
Provenance
Provenance details

First-party MCP

Tavily · Publisher source ↗

First-party MCP

Perplexity · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Jul 30, 2026

Package: Jul 27, 2026

Popularity evidence
GitHub starsNot documented

2,519

GitHub stars · checked 2026-09-08

Package downloads / 30 daysNo reliable download data

137,187

package downloads / 30 days · checked 2026-09-08

Client coverage
Client coverage detailsNot documented
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationHosted server supports OAuth flow or Tavily API key; API key may be supplied in URL or Authorization header.Hosted MCP and local stdio use a Perplexity API key. The hosted Streamable HTTP endpoint accepts Authorization: Bearer <API key>. The local HTTP transport uses PERPLEXITY_API_KEY for outbound Perplexity API calls but does not authenticate inbound MCP callers.
CostTavily account/API usage pricing and quotas apply.Perplexity API access is pay-as-you-go using separately purchased API credits; a Perplexity Pro subscription is not required. Search/research calls can incur API usage charges.
PermissionsPermissions are limited to Tavily service capabilities exposed by the MCP: search, extract, map, and crawl.The MCP is limited to four Perplexity search/reasoning/research tools. Effective quota and billing exposure are those of the supplied API key; it does not expose unrelated Perplexity account-management actions.
Data handlingQueries/URLs are sent to Tavily and results contain third-party web content.Queries are sent to Perplexity's Search API and Agent API and results are returned to the MCP client. Search/research output contains third-party web content and should be treated as untrusted external data.
Limitations
Tradeoffs
  • Read-oriented workflow lowers destructive risk, but web content can still contain prompt injection
  • Hosted service usage and quotas depend on Tavily account limits
  • The four-tool surface is focused and easier to reason about than broad browser MCPs, but requests and usage are billed through the Perplexity API Platform
  • The hosted remote server is easiest to operate; self-hosted HTTP requires the operator to secure inbound access because the server intentionally does not authenticate inbound callers
Risk contextMedium. Web content is untrusted; API credentials and recent dependency/security fixes should be revalidated before promotion.Medium. Protect the API key and monitor quota/cost. Web results can contain prompt injection. For self-hosted HTTP, default loopback/deny-all origin/host protections are important because inbound callers are otherwise unauthenticated.
Evidence date
Editorial review2026-09-112026-09-11
Candidate evidence2026-09-11T00:00:00.000Z2026-08-14T18:46:26.000Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →