Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LYNCEUS_API_KEYYesRequired API key for accessing the service. Obtain it at lynceus.ru.
LYNCEUS_API_URLNoOverride the API base URL for self-hosted deployments. Default is https://api.lynceus.ruhttps://api.lynceus.ru
LYNCEUS_TIMEOUT_MSNoPer-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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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:

  • query (required): search query, 1–10 words works best. Natural language questions are fine; keep the locale of the expected answers (query in Russian for Russian content).

  • freshness (optional): time = last ~hour, day = last 24h, week (default), month. Omit for no limit.

  • max_results (optional): 1–20, default 8.

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:

  • urls (required): 1–10 URLs. Batch related URLs in one call — cheaper and faster than one call per URL.

  • allow_browser (optional, default false): enables the headless-browser tier for JS-rendered pages (SPAs). Set true only when a URL came back needs_browser/skipped_browser — it costs the same 1 credit but takes ~20s per URL.

  • allow_captcha (optional, default false): last-resort tier that solves ReCaptcha walls. PREMIUM: 25 credits per URL. Only with explicit user consent.

  • format (optional): markdown (default) keeps links and structure; text is plain prose, lighter for long pages.

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DenSul/lynceus-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server