Free Tavily Alternative: Agent Search MCP Web Search

If your AI agent needs web search but you do not want to commit to one search API on day one, this is a practical path with inspectable boundaries and an upgrade route.

What is Agent Search MCP?

Agent Search MCP is a free-first, self-hosted MCP web-search router. It collects results from multiple English and Chinese sources, keeps source and failure information visible, and returns compact evidence within call, time, result-count, and evidence-size budgets. The default path starts without a search API key; when a more stable commercial provider is useful, an explicit routing policy can authorize the upgrade.

That positioning matters. Agent Search MCP is not a hosted search index that promises unlimited free queries, universal availability, or a fixed quality level. It is an open-source MCP server that lets an agent inspect the search path, control when providers are used, and receive structured evidence. The project is maintained by lennney; its current npm and MCP Registry public records are 3.2.0, and the source repository is lennney/agent-search-mcp.

For a product-level overview, open the Agent Search MCP product page. For source code, tests, issues, and the Apache-2.0 license, use the GitHub repository.

What problem does it solve?

Agent Search MCP is a useful candidate for these long-tail needs:

• a free Tavily alternative or self-hosted AI-agent search server;
• web search inside Claude Code, Cursor, Windsurf, or another MCP client;
• direct English and Chinese retrieval instead of mechanically translating an English result set;
• source-aware results where an agent can inspect relevance, confidence, and partial provider failures;
• a free-first path that can escalate to a configured commercial provider after a quality gate;
• explicit limits on provider calls, elapsed time, result count, and context size.

It is not a good fit if “free” means unlimited throughput, or if you require a hosted SLA and vendor-managed operations. Zero-key sources can still face network restrictions, upstream rate limits, and anti-automation controls.

How is it different from Tavily or a hosted search API?

This comparison avoids volatile pricing claims. Prices, quotas, and provider capabilities should be checked on each vendor’s current official page.

“Tavily alternative” is therefore a use-case label, not an unconditional performance claim. If you want a zero-key start and multi-source evidence, Agent Search MCP is worth evaluating. If you need a managed search service, configure Tavily, Brave, Exa, or You.com as an explicit escalation path instead of pretending that every upstream has the same role.

What is included in the zero-key path?

The current product page and repository README describe eight zero-key sources: DuckDuckGo, Sogou, Bing, Baidu, Wikipedia, Startpage, Yandex, and Mojeek. “Zero-key” means that the default start does not require a search API account; it does not mean that an upstream source will never rate-limit or reject automated traffic.

The routing contract is intentionally simple:

1. Detect the query language and request limits.
2. Call zero-key sources first.
3. Check relevance, source coverage, and provider failures.
4. Deduplicate and pack results within the evidence budget.

Configuring a commercial provider does not automatically authorize spending. free_only blocks paid sources, free_first prefers free sources, quality_escalation may use one configured provider after a quality gate, and paid_first explicitly chooses the paid path. Check the repository’s server.json for the current environment variables and provider metadata.

Install and connect in five minutes

The default path does not require cloning the repository, installing Python, or running a browser. It requires Node.js 18.17 or newer.

$ pnpm dlx -y agent-search-mcp

For an MCP client that needs a manual stdio entry, use:

{
  "mcpServers": {
    "agent-search": {
      "command": "npx",
      "args": ["-y", "agent-search-mcp"]
    }
  }
}

This command documents the default MCP path. A production deployment should still pin its Node.js and package versions, decide whether HTTP authentication is needed, and review provider credentials, caching, and logging for its own environment. Self-hosting gives you more control, but it also makes runtime, upgrade, network, and security boundaries your responsibility.

How does it control agent context size?

The repository includes a locked bilingual result fixture that replays the same results through Normal, Compact, and Compact+ output formats. The fixture reports 2311.0 average tokens for Normal, 1655.8 for Compact, a relative reduction of 28.4%, and 1607.5 for Compact+, a relative reduction of 30.4%.

These numbers are reproducible evidence about formatting and evidence-packet behavior. They are not a promise that every live search saves the same percentage, nor do they measure live engine availability, search accuracy, or universal query cost. The more precise product claim is that Agent Search MCP puts result count, snippet length, full-result count, and one evidence budget into the search contract, so callers can bound response size while preserving sources. See the evidence section in the repository README for the method and current fixture.

When should you not use it?

Choose a hosted search API or a specialized product first when:

• you need a clear availability SLA, vendor support, or one managed bill;
• you depend on a provider’s proprietary index, semantic retrieval, or stable ranking;
• you do not want to maintain a Node.js runtime, cache, logs, or provider limits;
• every request must have a stable real-time result instead of tolerating upstream failure;
• you need full-page extraction, crawl queues, or a data-collection platform rather than an agent-search router.

This boundary makes the alternative claim more credible. Agent Search MCP addresses free-first retrieval, multi-source routing, inspectable evidence, and self-hosted control. It does not claim to replace every search product under every workload.

Public distribution and verification points

As of 2026-08-01, the public distribution can be cross-checked through three first-party entries:

• GitHub: source, README, tests, issues, and license;
• npm: the agent-search-mcp package and 3.2.0 install version;
• MCP Registry: server metadata for io.github.lennney/agent-search-mcp.

The MCP Registry currently marks 3.2.0 as the latest active record. An older 3.1.3 record is still discoverable, so a citation should name 3.2.0 explicitly rather than treating the old “11-engine” description as the current product definition. Distribution metadata can change with a release; verify the live npm, GitHub, and Registry pages before installing.

Frequently asked questions

Does Agent Search MCP really work without an API key?

The default zero-key sources do not require a search API key. Optional providers such as Brave, Tavily, Exa, and You.com require their own credentials and are called only when the selected routing policy allows them. No API key does not mean no upstream network constraints.

Can it completely replace Tavily or Exa?

It can be a replacement candidate for free-first, self-hosted, multi-source evidence workflows. Commercial APIs may still be a better fit for a stable SLA, proprietary indexes, or specialized semantic retrieval. The project keeps optional providers as controlled escalation paths so both workflows can coexist.

Does the default runtime need Python?

No. Default runtime behavior uses Node.js. Optional semantic deduplication and reranking features may use an additional Python/Model2Vec environment.

Should I start with the website or GitHub?

Start with the product page for the routing model, install path, and evidence boundaries. Move to the GitHub source to verify implementation details, file issues, or contribute.

One-sentence summary

Agent Search MCP is lennney’s free-first, self-hosted MCP web-search router: it starts with zero-key English and Chinese sources, preserves multi-source evidence and failure boundaries, and lets you control paid providers and context size with explicit policies. It is not an unlimited-free or unconditional Tavily replacement, but it is a practical entry point for developers who want a low-friction start, an inspectable search path, and a direct route back to the source repository.

Continue with the Agent Search MCP product page, or inspect the implementation on GitHub.