# Sifthound

> Updated 2026-09-25 · type: tool · category: data-scraping · status: active · rev 1

Sifthound is a self-hosted, Tavily-compatible web search / extract / crawl / map API — plus an MCP server — for AI agents.

- Open source: yes (MIT)
- Self-hostable: yes
- Pricing model: free
- Best for: A team building agent enrichment or research flows that already codes against a Tavily-style search/extract API and wants to run that endpoint itself — an owned, self-hosted search layer with an MCP server — instead of paying per call to a hosted provider.
- Last verified: 2026-09-25

- **Canonical:** https://gtmstacker.com/registry/tool/sifthound/
- **Source:** [khsarvar · GitHub](https://github.com/khsarvar/sifthound)
- **Tags:** data-scraping, ai-infrastructure, self-hostable, mcp, search-api, tavily-compatible
- **Repository:** https://github.com/khsarvar/sifthound

## Is Sifthound open source?

Yes, Sifthound is open source under the MIT license.

## How much does Sifthound cost?

Sifthound is free to use.

## Can I self-host Sifthound?

Yes, Sifthound can be self-hosted (the source is available under the MIT license).


---

Sifthound is an MIT-licensed, self-hosted web search / extract / crawl / map API for AI agents, exposing a Tavily-compatible interface plus an MCP server. It is brand-new and unproven — created 2026-09-23, last pushed 2026-09-25, 0 stars — so treat it as a fresh drop, not an adopted tool. The value is that it is self-hostable: an owned endpoint you run rather than a paid search API you call.

## Provenance

- MIT (OSI-open); 0 stars, created 2026-09-23, last push 2026-09-25 (2 days old); a self-hosted, Tavily-compatible web search / extract / crawl / map API for AI agents, with an MCP server; self-hostable (WebFetch 2026-09-25).
- Surfaced via studio discovery in the 2026-09-25 pass.
- Anti-hype note: brand-new and unproven at 0 stars — represented as fresh, not adopted. Tavily-compatibility is the design goal; result parity is unverified.
- Curated from the GTM Stacker signal registry (2026-09-25 pass); license/facts independently verified 2026-09-25.

## Why it matters for a GTM stack

Agent enrichment and research flows lean on a search/extract API — usually a paid, hosted one billed per call. Sifthound's angle is to be that same shape of API, Tavily-compatible, but self-hosted: you run the endpoint, own the traffic, and swap it in wherever your agents already call a Tavily-style interface, with an MCP server on top. For a team doing agent-driven enrichment at volume, moving that layer in-house changes both the cost curve and the data-control story. The honest read: at 0 stars and two days old, this is a fresh drop with no adoption behind it — attractive as an owned alternative in principle, but the compatibility and extraction quality are unproven, so pilot it against your real workload before you build on it.