Skip to main content
Glama
DenSul

lynceus-mcp

by DenSul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to lynceus-mcp

No user-submitted related servers found.

    Related Servers

    • Yandex Search MCP Server by yandex

      Yandex Search MCP Serverofficial

      yandex
      F
      license
      Not graded
      quality
      F
      maintenance
      Enables AI assistants to perform real-time web searches and retrieve AI-generated answers using the Yandex Search API. It provides tools for accessing up-to-date internet information with support for both raw search results and summarized content via the Yazeka model.
      48
      -

    • yaseo

      novyiblog-tech
      A
      license
      B
      quality
      B
      maintenance
      Enables SEO and AI-search visibility analysis for Russian websites through Yandex APIs, including keyword research from Wordstat, live SERP results, position tracking with history, technical audits, content briefs, and checks of AI search citations.
      22
      2
      MIT

    • PowerSearch MCP

      theobjectivedad
      A
      license
      Not graded
      quality
      C
      maintenance
      Helps AI agents search the public web and fetch content with anti-bot measures, returning clean markdown outputs suitable for citation.
      2
      Apache 2.0
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    A4.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources