Tavily MCP
Production ready MCP server with real-time search, extract, map & crawl.
Is Tavily MCP safe? Promising trust profile, but some evidence still deserves review.
Compare Tavily MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Tavily MCP scores 67.6/100 (Grade B), ranked #422 of 1371 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; 62% of recent commits are signed; no published advisory affects its latest release (tavily-mcp); last pushed 2026-10-05. Every point is earned from checkable signals — never paid placement. How scoring works →
How Tavily MCP could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Publish build provenance for its packagesnpm publish --provenance from CI +14.7 → 82.3 A · #46 of 781
- Raise the OSSF Scorecard from 6.3 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, Security-Policy 0 +5.6 → 73.2 B · #168 of 781
- Sign every commit62% signed today +1.9 → 69.5 B · #216 of 781
Chain of custody
Scanners check what the code says. This traces who ships Tavily MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/tavily-ai/tavily-mcp, MIT, last pushed 2026-10-05. 62% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 6.3/10 (scanned Oct 10, 2026). The checks that decide who can get a change released:
- Code Review10
- Branch Protection6
- Signed Releasesn/a
- Dangerous Workflown/a
- Token Permissionsn/a
- Pinned Dependencies2
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 6CI-Tests 8CII-Best-Practices 0Code-Review 10Contributors 10Dangerous-Workflow -1Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging -1Pinned-Dependencies 2SAST 10Security-Policy 0Signed-Releases -1Token-Permissions -1Vulnerabilities 0 -
Published packages Linked, not attested
- npm tavily-mcp Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: tavily-mcp 0.2.22. No published advisory affects it (OSV, checked 2026-10-12).
Changes to this chain
- 2026-08-07 OSSF Scorecard: 6.6/10
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Tavily MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Tavily MCP compares in MCP Servers
- #248 Whoop MCP 67.8 +0.2
- #249 MCP Sitecore Server 67.8 +0.2
- #250 Tavily MCP 67.6 this agent
- #251 MCP Ts Core 67.6 ±0
- #252 MCP Open Library 67.6 ±0
Bars show each HVTrust score; the tick marks Tavily MCP’s 67.6.
Where the 67.6 comes from
HVTrust dimensions vs the MCP Servers average
67.6 / 100 · 100.0% confidenceTavily MCP MCP Servers average (781 agents)
Quick Trust Read
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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
65.5 / 100Common questions about Tavily MCP
Does Tavily MCP publish package provenance?
Does Tavily MCP have an OpenSSF Scorecard?
Is Tavily MCP actively maintained?
What license does Tavily MCP use?
Are Tavily MCP's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/tavily-mcp)
<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
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.4 · Raw JSON