Topic And Domain Filtered Search

via “advanced search with granular filtering and domain constraints”

Neural web search and content retrieval via Exa MCP.

Unique: Exposes Exa's full filter API through MCP tool parameters, allowing declarative specification of domain whitelists/blacklists, date ranges, and content categories without requiring direct API calls; filters are applied server-side before ranking

vs others: More flexible than Google Search API's site: operator; supports simultaneous multi-domain filtering, date ranges, and category constraints in a single query rather than requiring multiple searches

via “domain-filtered and depth-controlled search”

Search API for AI agents — clean web content, answer extraction, designed for RAG and LLM apps.

Unique: Offers explicit search depth controls and domain filtering as first-class features for agent builders, allowing fine-grained control over source trust and search comprehensiveness. Claimed in product description but implementation details absent from documentation.

vs others: More agent-centric than generic search APIs; provides explicit depth and domain controls rather than requiring post-processing filtering.

via “domain-filtering-and-source-restriction”

Neural search API — meaning-based search, full content retrieval, similarity search for AI agents.

Unique: Server-side domain filtering eliminates irrelevant results before returning to client, reducing token usage and improving result quality. Supports both include and exclude lists for flexible source control.

vs others: More efficient than client-side filtering because irrelevant results are eliminated server-side; reduces bandwidth and token usage compared to filtering results locally.

via “custom domain filtering and result reranking via goggles”

Independent search API — web, news, images, summarizer, privacy-respecting, free tier.

Unique: Brave's Goggles feature allows application-level result filtering and reranking without modifying the search query itself, enabling dynamic source prioritization and content moderation rules that can be updated independently of application code. This is distinct from query-level filtering (site: operators) because it operates on the result set after ranking, allowing more sophisticated control.

vs others: More flexible than Google Custom Search's domain whitelisting because it supports reranking and prioritization, not just inclusion/exclusion, and can be modified per-request rather than being baked into a static search engine configuration.

via “parameterized search with query refinement”

MCP server for advanced web search using Tavily

Unique: Exposes Tavily's advanced query parameters (search_depth, domain filtering) as MCP tool parameters, allowing Claude and agents to refine searches programmatically without prompt engineering. Supports both positive (include) and negative (exclude) domain filtering in a single call.

vs others: More flexible than basic keyword search because it supports domain-level filtering; more efficient than post-processing results because filtering happens server-side before returning to the client.

via “advanced web search with granular filtering”

Exa MCP for web search and web crawling!

Unique: Exposes Exa's advanced filtering capabilities (domain whitelisting, date ranges, content categories) through a structured MCP tool parameter schema, allowing clients to declaratively specify search constraints without constructing complex query syntax. The server translates structured filter objects into Exa API query parameters.

vs others: Provides declarative, structured filtering via MCP tool parameters, whereas generic search APIs require query string syntax or separate API calls; enables researchers to enforce source and temporal constraints programmatically within agent workflows.

via “search query optimization and parameter tuning”

MCP server for advanced web search using Tavily

Unique: Exposes Tavily's full parameter set through MCP tool schema with validation, allowing LLM agents to dynamically adjust search strategy without hardcoding. Includes topic mode selection (general vs news) and domain filtering, enabling context-aware search adaptation.

vs others: More flexible than simple keyword search, allows agents to self-optimize queries based on task requirements, and provides server-side filtering that reduces irrelevant results before returning to client.

via “contextual filtering of search results”

Highest accuracy web search for AIs

Unique: Utilizes session context to dynamically adjust result relevance, providing a personalized search experience that adapts over time.

vs others: More personalized than standard search engines, as it evolves based on user interactions and preferences.

via “parameterized search filtering and refinement”

** - Self-hosted Websearch API

Unique: Exposes filter parameters through the MCP tool schema (domain, language, region, exclude_terms) that are evaluated server-side by the Crawler API, enabling declarative result filtering without requiring the client to implement post-processing logic

vs others: Provides server-side filtering integrated into the search request, unlike REST search APIs that return unfiltered results requiring client-side post-processing, and unlike simple HTTP crawlers that have no filtering capability

via “topic-and-domain-filtered-search”

Use this MCP server to search barnsworthburning.net, a digital commonplace book built and curated by Nick Trombley. The site contains a wealth of bookmarks and short snippets on a broad range of topics: design, software, art, architecture, craft, writing, literature, and many more.

Unique: Leverages the curator's editorial domain taxonomy to enable structured filtering, rather than relying on generic keyword matching or learned embeddings. This ensures that domain boundaries reflect human judgment about knowledge organization.

vs others: More precise than keyword-based filtering because it respects the curator's intentional categorization, avoiding false positives from polysemous terms (e.g., 'design' in software vs. graphic design contexts).

via “tld filtering for domain search”

MCP server: domain-search-mcp

Unique: The ability to filter by TLDs directly within the MCP framework allows for more precise searches compared to generic domain search APIs.

vs others: More customizable than standard domain search APIs, which often return results across all TLDs without filtering options.

via “custom search filters and result refinement”

A search engine built on AI that provides users with a customized search experience while keeping their data 100% private.

via “domain and content-type filtering with whitelist/blacklist”

Language model powered search.

Unique: Applies domain and content-type filtering server-side during ranking, reducing irrelevant results before returning to client. Enables focused searches without post-processing filtering.

vs others: More efficient than client-side filtering (reduces data transfer and processing); server-side filtering ensures ranking is aware of constraints, improving result quality vs. post-hoc filtering.

via “source-specific search filtering”

via “metadata-filtering-on-vector-queries”