Payx Tavily Search

io.github.Swathi-MuraliSrinivasanPublished by GitHub account Swathi-MuraliSrinivasanv0.1.0Updated Oct 24, 2026

FastMCP server for Tavily search API with web search and content extraction

VerifiedSTDIODesktop onlyWeb Search & Scraping

Overview

AI-generated overview

A local FastMCP server that gives an assistant Tavily-powered web search and content extraction.

What you can do
It wraps the Tavily search API in a FastMCP server, exposing web search and content extraction as tools an assistant can call. The assistant can run searches and pull readable content from pages through those tools. It runs as a local process on the user's machine over stdio.
When to use it
Worth adding when an assistant needs live web search results or extracted page content rather than relying on its own training data. Suitable for research, fact-checking, and gathering current information during a task.
Requirements
Runs as a local process over stdio, so a local runtime able to start a FastMCP server is needed. The manifest declares no packages, environment variables, headers, or authentication, but the underlying Tavily search API normally requires an API key, which is not declared here. Network access is needed to reach Tavily.
Before you install
The manifest declares no authentication and no environment variables, yet the server depends on the Tavily search API, which typically needs an API key; how that credential is supplied is not stated. Search queries and extracted page content are sent to Tavily as a third party. Desktop only, with no web executable.

Installation

In SourceWeft

  1. Open Payx Tavily Search in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.