Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Tavily

NPM · @PIPEWORX/MCP-TAVILY · 2 COMPONENTS

Tavily MCP — wraps the Tavily API (tavily.com)

0 this week 79 Trust /100

Last scanned (7 hours ago)

Scores higher than 62% of npm servers

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-tavily). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 628 tokens (~209/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 79

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-tavily@0.2.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-tavily
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-tavily/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3560378339
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:5e96de5dccb104280e80661b9da6d379ae7cd41a280645e0f9d271d84d318b3c2fa448a9d6c7ba041849eb3e1ed05d6334e94b78f36c63d9b63250da8

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~575 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
extract ~115

Extract clean article text from one or more URLs via Tavily: strips boilerplate/navigation and returns up to 20,000 chars of readable content per page. Accepts a single URL string or an array. Ideal for feeding source pages into an LLM.

NameTypeReqDescription
_apiKeystring–Optional — your own Tavily API key for higher limits; omit to use the shared Pipeworx key.
urlsstring|arrayyesA single URL string, or an array of URL strings, to extract clean text from.

No output schema declared.

No examples provided.

search ~216

AI/LLM-optimized web search built for RAG: returns a synthesized natural-language answer plus a ranked list of sourced results (title, url, content snippet, relevance score). Prefer this over scraping a generic search engine when you need grounded, citable web context. Example: search({ query: "latest SpaceX Starship test result" })

NameTypeReqDescription
_apiKeystring–Optional — your own Tavily API key for higher limits; omit to use the shared Pipeworx key.
include_answerboolean–Whether to include a synthesized AI answer string (default true).
max_resultsnumber–Maximum number of results to return (default 5, max 20).
querystringyesThe search query / question to research.
search_depthstring–Search depth: "basic" (fast, default) or "advanced" (deeper, more thorough).
topicstring–Search topic: "general" (default) or "news" for recent news coverage.

No output schema declared.

No examples provided.

tavily_news ~244

Recent NEWS coverage with FULL ARTICLE TEXT — "latest news about <company/person/topic>", "news coverage of X this week", "what are people reporting about X", "recent headlines on X". Returns a synthesized answer plus ranked articles each carrying title, url, publication content, and a relevance score — the full text, not just a headline, so the calling agent can quote and cite. Freshness-windowed via `days` (default 7). This is the premium news path (Tavily, funded key, no per-IP throttle, no shared free-tier quota); prefer it when the question asks what is being REPORTED about a specific entity or topic.

NameTypeReqDescription
_apiKeystring–Optional — your own Tavily API key for higher limits; omit to use the shared Pipeworx key.
daysnumber–How many days back to search (default 7, max 30).
max_resultsnumber–Maximum number of articles (default 5, max 20).
querystringyesThe entity or topic to get news about, e.g. "Anthropic", "GLP-1 drug pricing".

No output schema declared.

No examples provided.

Install

How do I install the Tavily MCP server?

Tavily runs locally as an npm package, launched with npx -y @pipeworx/mcp-tavily. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-tavily

# add to Claude Code
claude mcp add pipeworx-io-tavily -- npx -y @pipeworx/mcp-tavily
Common questions

What is the Tavily MCP server?

Tavily is an MCP server listed in the public MCP registry as io.github.pipeworx-io/tavily. Tavily MCP, wraps the Tavily API (tavily.com). This page covers its npm package (@pipeworx/mcp-tavily).

Is the Tavily MCP server safe to use?

Tavily scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Tavily MCP server expose?

Tavily exposes 3 tools: search, tavily_news, extract. Their descriptions and schemas cost roughly 575 tokens of context every time the server is loaded.

Is the Tavily MCP server still maintained?

Tavily is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Tavily MCP server under?

Tavily declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.