Skip to main content
Glama
NISH1001

abyss-mcp

by NISH1001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to abyss-mcp

No user-submitted related servers found.

    Related Servers

    • jupsearch-mcp

      4cya
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to run unified web searches across multiple providers such as Exa, Serper, Tavily, Firecrawl, and Jina, fusing results with reciprocal rank fusion, and to extract readable content from public web pages, PDFs, and video pages as Markdown. Provider chains are configurable, failures are isolated per provider, and responses report attempted, succeeded, failed, and skipped channels with source tracing and honest warnings.
      MIT

    • mcp-deepseek-search

      Matthewyin
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes DeepSeek's web search and page-fetch tools to any MCP client, letting any LLM run searches with quality signals like rerank score and source authority, plus advanced query syntax. It also retrieves single pages as Markdown, with built-in throttling, retries, and size-conscious summaries.
      MIT

    • CrawlEyes

      waiky-github
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to perform web searches and extract full-text content from web pages via standard MCP tools, with fallback search and semantic reranking.
      2
      2
      MIT

    • groundlink-mcp

      ohhavefun
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP hosts to perform cited web searches and receive source-bearing results with titles, URLs, snippets, and sources for evidence-grounded answers.
      1
      15 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of an agent confusing it with another action. Its purpose ('search the web') is unambiguous.

    Naming Consistency4/5

    The single name 'search' is a clean, conventional verb choice, but with only one tool there is no pattern to demonstrate consistency against.

    Tool Count3/5

    A one-tool server is inherently thin; even for a narrow web-search purpose, a single tool leaves no room for query variants, site scoping, or content retrieval.

    Completeness3/5

    Search returning only URLs and snippets covers the stated core purpose, but there is no way to fetch or read page contents, which is a common dead end for an agent needing current information.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources