Cluefinch MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_SEARCH_ENGINES | No | Allowed explicit engine subset; omitting engines uses SearXNG defaults | google,google cse,brave,wikipedia,wikidata |
| MCP_SEARCH_FETCH_TTL | No | Lifetime of fetched pages in the local cache, in seconds | 600 |
| MCP_SEARCH_SEARCH_TTL | No | Lifetime of search results in the local cache, in seconds | 300 |
| MCP_SEARCH_MAX_QUERIES | No | Maximum number of search queries in one research_collect call | 10 |
| MCP_SEARCH_MAX_RESULTS | No | Maximum number of results per search | 20 |
| MCP_SEARCH_MAX_SOURCES | No | Maximum number of sources research_collect may attempt to collect | 10 |
| MCP_SEARCH_SEARXNG_URL | No | SearXNG address | http://127.0.0.1:8081 |
| MCP_SEARCH_MAX_TEXT_CHARS | No | Maximum amount of extracted text retained for one page | 100000 |
| MCP_SEARCH_MAX_FETCH_CHARS | No | Maximum size of a single returned page fragment | 20000 |
| MCP_SEARCH_FETCH_CONCURRENCY | No | Maximum number of concurrent page fetches | 3 |
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 |
|---|---|
| web_searchA | Discover candidate sources through search; this does not fetch page content. |
| web_fetchA | Read one selected HTML document as bounded Markdown text. |
| web_linksA | Navigate from a known HTML page to pages that it explicitly links. |
| research_collectA | Collect bounded evidence from several selected or searched sources. |
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 4 tools
Each tool has a clearly distinct purpose: web_search for discovery, web_fetch for reading one document, web_links for navigating known HTML pages, and research_collect for multi-source evidence gathering. The descriptions explicitly state when to use each and include 'DO NOT' guidance to prevent misuse, leaving no ambiguity.
Three tools follow a web_ prefix pattern, but research_collect deviates. Verb forms are also mixed: web_search and web_fetch are verb-based, web_links is noun-based, and research_collect combines noun+verb. All are snake_case and readable, but the pattern is not fully consistent.
Four tools is well-scoped for a web research server. Each tool serves a distinct, non-redundant function—discovery, single-document reading, link navigation, and multi-source collection—so every tool earns its place without bloat or thinness.
The surface covers the core lifecycle of web research: discovery, navigation, reading, and multi-source evidence gathering. A minor gap is the absence of any crawling or bulk link-following tool, though the descriptions intentionally exclude crawling, making it a reasonable scope boundary rather than a critical omission.