updated 2026-08-09 19:01 UTC

Tavily MCP

tavily-ai/tavily-mcp

Production ready MCP server with real-time search, extract, map & crawl.

MCP Servers JavaScript Grade B Listed MIT
68.7/100
Rank #146 of 1204
Compare Tavily MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-09 · 0d ago
Recent change
Rank +2

Is Tavily MCP safe? Tavily MCP scores 68.7/100 (Grade B), ranked #146 of 1204 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.3/10; 64% of recent commits are signed; last pushed 2026-08-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#30 Google Analytics MCP — 69.0 (B) → #31 MCP Server Polarion — 68.8 (B) → #33 Discord MCP — 68.7 (B) → #34 MCP Server Couchbase — 68.6 (B) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-08
Rank Moved
Rank dropped 25 spots (#122 → #147)
2026-08-07
Provider Removed
Runtime surface shrank — no longer detected: Anthropic
2026-08-07
Scorecard Added
OSSF Scorecard: 6.6/10
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.3/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent Get email alerts for Tavily MCP View MCP Servers Report missing data
67.9
Activity sub-score · out of 100
#32
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-09 19:01 UTC · Repo last pushed today

Activity & Reach

Stars
2.3k
Forks
285
Last Push
2026-08-09
today
Commits (4 wk)
7?
Downloads (7d)
35,945
npm
HN mentions (30d)
—
Open Issues
30
Rank Change
▲1
was #147

Analysis

HVTrust Dimensions vs MCP Servers

68.7 / 100 · 100.0% confidence

Tavily MCP MCP Servers average (718 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.1 / 25
6.0 above avg 5.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.5 below avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
13.9 / 17
5.1 above avg 8.8
Maintenance60% last-push freshness · 40% commit activity
13.8 / 20
1.3 above avg 12.5
AdoptionLog-scaled stars · package downloads
14.1 / 20
8.6 above avg 5.5

Activity Inputs

67.9 / 100
StarsRepository reach
20.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
11.3 / 25
CommunityFork signal
11.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
6.3 / 10
OpenSSF Scorecard · scanned Aug 9, 2026
Signed Commits
64%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 6
CI-Tests 5
CII-Best-Practices 0
Code-Review 10
Contributors 6
Dangerous-Workflow -1
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 2
SAST 10
Security-Policy 0
Signed-Releases -1
Token-Permissions -1
Vulnerabilities 2

Is Tavily MCP safe?

Tavily MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Tavily MCP publish package provenance?
No published build provenance is currently detected for Tavily MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Tavily MCP have an OpenSSF Scorecard?
Tavily MCP has an OpenSSF Scorecard score of 6.3/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Tavily MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Tavily MCP use?
Tavily MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Tavily MCP's commits signed?
64% of the last 100 commits to Tavily MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Tavily MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Tavily MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-08-07
Provider Removed
Runtime surface shrank — no longer detected: Anthropic

Maintain Tavily MCP?

For maintainers

HVTrust scores Tavily MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 3Listed 1Scorecard 1Surface 1
2026-08-08
Rank Moved
Rank dropped 25 spots (#122 → #147)
2026-08-07
Provider Removed
Runtime surface shrank — no longer detected: Anthropic
2026-08-07
Scorecard Added
OSSF Scorecard: 6.6/10
2026-07-29
Rank Moved
Rank dropped 11 spots (#378 → #389)
2026-07-15
Rank Moved
Rank dropped 25 spots (#350 → #375)
2026-07-14
Newly Listed
First tracked at rank #350
GitHub → npm: tavily-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 68.7 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/tavily-mcp.svg)](https://hvtracker.net/agents/tavily-mcp)
HTML:
<a href="https://hvtracker.net/agents/tavily-mcp"><img src="https://hvtracker.net/badge/tavily-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON