Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-18 15:18 UTC

tavily-ai / tavily-mcp

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

TypeScriptMIT★ 2,496 stars⑂ 310 forkssince Jan 2025View on GitHub ↗
KindCommand-line toolMCP serverLibraryhow this is determined

tavily-ai/tavily-mcp holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (71/100) and lowest on Engineering Quality (37/100). It was last updated today. 2 contributors account for most of its recent work.

65
overall / 100
Good

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

65
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 60 is calibrated to 65 on the published index scale (record calibration 2026-08-02).

Ownership

Tavily AIOrganization
1,011 followers45 public repossince May 2024

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

54Moderate · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
24.9/36Commit cadence — 36/52 weeks with commits
18/18Commit volume — 160 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year160
human_commit_share0.77
days_since_last_push0
active_weeks_last_year36
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

70Good · 17% of overall
How it's scored
55.1/60Stars — 2,496 stars
20.8/25Forks — 310 forks
4.3/15Watchers — 7 watchers
Inputs used
forks310
stars2,496
watchers7
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
66.1/80Monthly downloads — 90,682 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagestavily-mcp
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads90,682
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

71Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
15.3/22.5Commit distribution — top contributor authored 32% of commits
13.5/13.5Contributor breadth — 17 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor2
contributors_sampled17
top_contributor_share0.32
How it's scored
18.4/42Issue resolution — 44% of issues closed
19.8/30PR acceptance — 93/141 decided PRs merged
13/13Newcomer PR acceptance — 2/2 first-time contributors' PRs merged in 30d
9/15OpenSSF Scorecard: Code-Review — Found 3/5 approved changesets -- score normalized to 6
Inputs used
merged_prs93
open_issues40
closed_issues31
prs_merged_7d1
prs_decided_7d1
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.437
closed_unmerged_prs48
first_time_authors_30d2
first_time_prs_merged_30d2
first_time_prs_decided_30d2
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
21.6/25Owner reach — 1,011 followers of tavily-ai
17.1/25Track record — 45 public repos, account ~2 yr old
Inputs used
followers1,011
owner_typeOrganization
is_verifiedno
owner_logintavily-ai
public_repos45
account_age_days913

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 104 days ago
20/20Version history — 28 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagestavily-mcp
ecosystemsnpm
any_deprecatedno
min_days_since_publish104

Engineering Quality

Are baseline engineering and documentation practices in place?

37Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests — 3 out of 11 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

67Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
4.5/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0.5/2.5CI-Tests — 3 out of 11 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-Review — Found 3/5 approved changesets -- score normalized to 6
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
0/10Dangerous-Workflow — no data
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
1/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
5/5SAST — SAST tool is run on all commits
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate6.7
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. Remaining weights renormalized.
How it's scored
10.9/35Direct dependencies free of known advisories — 1 affected: @modelcontextprotocol/sdk 1.26.0 (high 8.6)
14.4/25Indirect dependencies free of known advisories — 1 affected: @hono/node-server 1.19.18 (moderate 5.3)
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories7
affected_packages2
assessed_packages125
unassessed_packages0
affected_by_severityhigh 1, moderate 1
direct_affected_packages1
Matched the npm:tavily-mcp@0.2.22 runtime dependency closure — what installing the published package pulls in — 125 packages. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

62Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.anthropic.com/llms.txt)
40/40Legible commit history — 65 of 77 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.anthropic.com/llms.txt
legible_history_share0.844
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — tsconfig.json
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 5 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 22 of the last 100 commits are automated dependency updates
2/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0.05
toolchain_manifests—
dependency_bot_commit_share0.22
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/5 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes50,059
source_files_sampled5
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalyes
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

2,496GitHub stars
17contributors
160commits, last 12 months
0days since last push
0releases
2bus factor
40open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 310 ⇿
0Stars
310Forks

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

012525037530862025-012025-122026-11

Each point covers 2 days.

OpenSSF Scorecard 6.7 / 10
6.7aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-11-18 15:18 UTC

10Binary-Artifactsno binaries found in the repo
6Branch-Protectionbranch protection is not maximal on development and all release branches
2CI-Tests3 out of 11 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 3/5 approved changesets -- score normalized to 6
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
npm@modelcontextprotocol/sdk1.32.0package.json
npmdotenv^16.4.5package.json
npmaxios^1.6.7package.json
npmyargs^17.7.2package.json
All dependencies 128

Full resolved dependency set from the GitHub dependency graph: 4 direct and 124 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
npm@modelcontextprotocol/sdk1.32.0direct
npmaxios1.20.0direct
npmdotenv16.5.0direct
npmyargs17.7.2direct
npm@hono/node-server2.1.8indirect
npm@types/node20.17.46indirect
npm@types/yargs17.0.33indirect
npm@types/yargs-parser21.0.3indirect
npmaccepts2.0.0indirect
npmagent-base6.0.2indirect
npmajv8.18.0indirect
npmajv-formats3.0.1indirect
npmansi-regex5.0.1indirect
npmansi-styles4.3.0indirect
npmasynckit0.4.0indirect
npmbody-parser2.4.0indirect
npmbytes3.1.2indirect
npmcall-bind-apply-helpers1.0.2indirect
npmcall-bound1.0.4indirect
npmcliui8.0.1indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcombined-stream1.0.8indirect
npmcontent-disposition1.0.1indirect
npmcontent-type1.0.5indirect
npmcontent-type2.0.0indirect
npmcontent-type2.1.0indirect
npmcookie0.7.2indirect
npmcookie-signature1.2.2indirect
npmcors2.8.5indirect
npmcross-spawn7.0.6indirect
npmdebug4.4.3indirect
npmdelayed-stream1.0.0indirect
npmdepd2.0.0indirect
npmdunder-proto1.0.1indirect
npmee-first1.1.1indirect
npmemoji-regex8.0.0indirect
npmencodeurl2.0.0indirect
npmes-define-property1.0.1indirect
npmes-errors1.3.0indirect
npmes-object-atoms1.1.1indirect
npmes-set-tostringtag2.1.0indirect
npmescalade3.2.0indirect
npmescape-html1.0.3indirect
npmetag1.8.1indirect
npmeventsource3.0.7indirect
npmeventsource-parser3.0.6indirect
npmexpress5.2.1indirect
npmexpress-rate-limit8.5.1indirect
npmfast-deep-equal3.1.3indirect
npmfast-uri3.1.9indirect
npmfinalhandler2.1.1indirect
npmfollow-redirects1.16.2indirect
npmform-data4.0.6indirect
npmforwarded0.2.0indirect
npmfresh2.0.0indirect
npmfunction-bind1.1.2indirect
npmget-caller-file2.0.5indirect
npmget-intrinsic1.3.0indirect
npmget-proto1.0.1indirect
npmgopd1.2.0indirect
npmhas-symbols1.1.0indirect
npmhas-tostringtag1.0.2indirect
npmhasown2.0.4indirect
npmhono4.13.18indirect
npmhttp-errors2.0.1indirect
npmhttps-proxy-agent5.0.1indirect
npmiconv-lite0.7.3indirect
npminherits2.0.4indirect
npmip-address10.7.5indirect
npmipaddr.js1.9.1indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-promise4.0.0indirect
npmisexe2.0.0indirect
npmjose6.1.3indirect
npmjson-schema-traverse1.0.0indirect
npmjson-schema-typed8.0.2indirect
npmmath-intrinsics1.1.0indirect
npmmedia-typer1.1.0indirect
npmmerge-descriptors2.0.0indirect
npmmime-db1.52.0indirect
npmmime-db1.54.0indirect
npmmime-types2.1.35indirect
npmmime-types3.0.2indirect
npmms2.1.3indirect
npmnegotiator1.0.0indirect
npmobject-assign4.1.1indirect
npmobject-inspect1.13.4indirect
npmon-finished2.4.1indirect
npmonce1.4.0indirect
npmparseurl1.3.3indirect
npmpath-key3.1.1indirect
npmpath-to-regexp8.4.0indirect
npmpkce-challenge5.0.1indirect
npmproxy-addr2.0.8indirect
npmproxy-from-env2.1.0indirect
npmqs6.16.1indirect
npmrange-parser1.2.1indirect
npmraw-body3.0.2indirect
npmrequire-directory2.1.1indirect
npmrequire-from-string2.0.2indirect
npmrouter2.2.0indirect
npmsafer-buffer2.1.2indirect
npmsend1.2.1indirect
npmserve-static2.2.1indirect
npmsetprototypeof1.2.0indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmside-channel1.1.1indirect
npmside-channel-list1.0.1indirect
npmside-channel-map1.0.1indirect
npmside-channel-weakmap1.0.2indirect
npmstatuses2.0.2indirect
npmstring-width4.2.3indirect
npmstrip-ansi6.0.1indirect
npmtoidentifier1.0.1indirect
npmtype-is2.1.0indirect
npmtypescript5.8.3indirect
npmundici-types6.19.8indirect
npmunpipe1.0.0indirect
npmvary1.1.2indirect
npmwhich2.0.2indirect
npmwrap-ansi7.0.0indirect
npmwrappy1.0.2indirect
npmy18n5.0.8indirect
npmyargs-parser21.1.1indirect
npmzod4.6.7indirect
npmzod-to-json-schema3.25.1indirect
Dependency advisories 2

Installing npm:tavily-mcp@0.2.22 pulls in 125 packages, direct and transitive: 2 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
@modelcontextprotocol/sdk1.26.0directhigh62.3.1
@hono/node-server1.19.18indirectmoderate12.1.3

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.