Is Tavily MCP safe to use?

Tavily MCP has an HVTrust score of 70.1/100 (Grade B), ranked #173 of 1316 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Tavily MCP?

Tavily MCP scores 70.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.4k GitHub stars and is categorized under MCP Servers.

Tavily MCP

tavily-ai/tavily-mcp

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

MCP Servers JavaScript Grade B Listed MIT

70.1/100

Rank #173 of 1316

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-20 · 9d ago

Recent change

Rank +1

Is Tavily MCP safe? Tavily MCP scores 70.1/100 (Grade B), ranked #173 of 1316 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 7.3/10; 64% of recent commits are signed; last pushed 2026-08-20. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#54 Edinet MCP — 70.6 (B) → #55 Firecrawl MCP Server — 70.2 (B) → #57 ZulipChat MCP Server — 70.0 (B) → #58 YADE MCP Server — 69.7 (B) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-26

Rank Moved

Rank dropped 20 spots (#139 → #159)

2026-08-22

Rank Moved

Rank rose 10 spots (#140 → #130)

2026-08-21

Rank Moved

Rank rose 26 spots (#166 → #140)

Maintainer Checklist

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

66.1

Activity sub-score · out of 100

#56

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 →

Rank Trend

2026-08-11 2026-08-29

Activity & Reach

Stars

2.4k

Forks

291

Last Push

2026-08-20

9 days ago

Commits (4 wk)

Downloads (7d)

35,945

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼3

was #170

Analysis

HVTrust Dimensions vs MCP Servers

70.1 / 100 · 100.0% confidence

Tavily MCP MCP Servers average (777 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

12.3 / 25

5.4 above avg 6.9

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.5 below avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

14.7 / 17

4.6 above avg 10.1

Maintenance60% last-push freshness · 40% commit activity

13.1 / 20

0.9 above avg 12.2

AdoptionLog-scaled stars · package downloads

14.2 / 20

8.4 above avg 5.8

Activity Inputs

66.1 / 100

StarsRepository reach

20.2 / 30

FreshnessLast push recency

23.8 / 25

ActivityRecent commits

10.5 / 25

CommunityFork signal

11.5 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

7.3 / 10

OpenSSF Scorecard · scanned Aug 26, 2026

Signed Commits

64%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 6

CI-Tests 6

CII-Best-Practices 0

Code-Review 10

Contributors 10

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 10

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 7.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?

Maintained. Last push was 9 days ago.

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.

Tavily

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

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

2026-08-26

Rank Moved

Rank dropped 20 spots (#139 → #159)

2026-08-22

Rank Moved

Rank rose 10 spots (#140 → #130)

2026-08-21

Rank Moved

Rank rose 26 spots (#166 → #140)

2026-08-12

Rank Moved

Rank rose 12 spots (#167 → #155)

2026-08-10

Rank Moved

Rank dropped 13 spots (#151 → #164)

2026-08-08

Rank Moved

Rank dropped 25 spots (#122 → #147)

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

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.3 · Raw JSON