trailsearch-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| trailsearch_searchA | Search the web through a self-hosted TrailSearch API (SearXNG-backed, Tavily-compatible). Args: query: search query string. max_results: number of results to return (1-20, default 5). mode: "search" (fast, results only) or "crawl" (also fetches page content). search_depth: "basic" or "advanced". include_answer: request a short synthesized answer. include_domains: only include results from these domains. exclude_domains: skip results from these domains. days: restrict results to the last N days (1/7/30/365). topic: optional topic hint (e.g. "news"). Returns: JSON string with the search results (title, url, content/snippet, score). |
| trailsearch_extractB | Fetch clean content from known URLs via the TrailSearch /extract endpoint. Args: urls: list of URLs to extract content from. query: optional context query used while extracting. include_raw_content: also return raw (unfiltered) content per URL. Returns: JSON string with the extracted content for each URL. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one performs web searches, the other extracts content from known URLs. There is no overlap or ambiguity between them.
Both tools follow a consistent 'trailsearch_' prefix followed by a verb in lowercase snake_case, which is used uniformly. This matches a clear and predictable pattern.
With only two tools, the server feels minimal, though it covers the essential search and extraction workflow. The low count is borderline and fits the 'thin' end of the scale.
The pair provides solid coverage of search and content extraction, with search supporting many filters and answer generation. Minor gaps exist (e.g., no dedicated endpoint for querying recent trends or managing custom indices), but core user needs are met.