lynceus-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LYNCEUS_API_KEY | Yes | Required API key for accessing the service. Obtain it at lynceus.ru. | |
| LYNCEUS_API_URL | No | Override the API base URL for self-hosted deployments. Default is https://api.lynceus.ru | https://api.lynceus.ru |
| LYNCEUS_TIMEOUT_MS | No | Per-call timeout in milliseconds. Default is 120000. | 120000 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lyn_searchA | Search the live web via Lynceus (RU-web-first: the Yandex index, strong on Russian-language and .ru content; English/world queries also work). WHEN TO USE: you need fresh URLs, titles and snippets to answer questions about anything current or web-specific — news, docs, prices, people, Russian sites that Google-based tools under-cover. Use BEFORE lyn_extract when you don't yet have the URLs. ARGUMENTS:
COST: 1 credit per request. Cached results still return full data. RETURNS: numbered list — rank, title, URL, snippet, published date when known. Snippets are short; call lyn_extract on the promising URLs for the actual text. FAILURES: engine_upstream (retry once), 401 (bad API key), 402 (out of credits — tell the user). |
| lyn_extractA | Fetch web pages and get their content as clean, reader-mode Markdown via Lynceus' 4-tier anti-bot ladder (Chrome TLS fingerprint → site adapters → headless browser → captcha solving). Works on pages that return 403/paywall-shell/empty content to naive fetchers. WHEN TO USE: you have URLs (from lyn_search or the user) and need the actual text — articles, docs, blog posts, discussions. Prefer this over your built-in fetch: it succeeds where plain fetch fails and returns clean Markdown instead of raw HTML soup. ARGUMENTS:
COST: 1 credit per successfully extracted URL. Cache hits (same URL within the TTL) are free and marked cached:true. Failed URLs are never charged. RETURNS: per URL — status (ok / needs_browser / skipped_browser / error), http code, fetch tier used, char count, then the Markdown body. needs_browser means: retry with allow_browser:true if you need that page. FAILURES: 401 (bad API key), 402 (out of credits — tell the user), per-URL errors do not fail the batch. |
| lyn_usageA | Check the Lynceus account's remaining credits. Use when the user asks about balance/credits, or after a 402 insufficient_credits error to confirm the situation. Free; no side effects. |
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 3 tools
Each tool has a distinct, non-overlapping purpose: lyn_search finds URLs, lyn_extract retrieves page content, and lyn_usage checks credits. There is no ambiguity about which tool to use for a given task.
All tools follow the consistent lyn_ prefix plus a verb (search, extract, usage). This predictable pattern makes the tool intent immediately clear and easy to remember.
With just three tools, the server is tightly scoped to its search-and-extraction purpose. Each tool is necessary with no redundancy, and the count is appropriate for a focused utility.
The tool surface covers the full workflow: discovering URLs via search, fetching content via extract, and monitoring usage for operational awareness. No obvious gaps exist for the stated purpose.