Skip to main content
Glama
Sign In
yeivily-mcp

yeivily-mcp

by yeib
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to yeivily-mcp

No user-submitted related servers found.

    Related Servers

    • oxe

      espetro
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to perform local web searches through DuckDuckGo, with a shared TTL cache and user click history via an Exa-compatible API.
      5
      -

    • MCP Web Tools

      SayreBlades
      F
      license
      A
      quality
      D
      maintenance
      Provides local web search and content fetching capabilities for AI assistants, enabling them to search DuckDuckGo and extract clean text from web pages. All requests originate from the user's machine to ensure direct network control and bypass external proxies.
      2
      -

    • free-search-mcp-ts

      lhswgzy
      A
      license
      A
      quality
      C
      maintenance
      Enables any MCP client to run keyless multi-engine web searches with RRF fusion, fetch pages and documents as Markdown, and full-text search a local SQLite index. It keeps queries and cached content on the user's machine, degrading gracefully across engine tiers when providers are blocked or rate-limited.
      8
      MIT

    • keyless-web-search-mcp

      dollarser
      F
      license
      A
      quality
      C
      maintenance
      Enables keyless web search across multiple engines with fallback and relevance ranking, plus anonymous HTTP(S) page fetching, all without API keys or vendor dependencies.
      2
      1
      -

    • privatesearch

      CloudCorpRecords
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to search the web via DuckDuckGo's public HTML endpoint and fetch pages as plain readable text, without requiring an account, API key, or search subscription.
      298 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

    A4.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools cover clearly disjoint steps of a retrieval workflow: web_search discovers URLs and fetch_page reads a known URL. Descriptions even cross-reference each other, making the intended pipeline unambiguous.

    Naming Consistency5/5

    Both names follow a consistent snake_case verb_noun pattern (web_search, fetch_page). The only nuance is that web_search puts the resource before the verb, but the two names still read as a coherent, predictable pair.

    Tool Count4/5

    Two tools is minimal but each earns its place in a search-then-read workflow, with no redundancy. It is slightly thin for a standalone server, since filters or pagination would otherwise be separate tools.

    Completeness4/5

    Search plus fetch covers the core web-retrieval lifecycle with no dead ends for the stated scope. Gaps exist but are documented (no PDF reading, no JavaScript, no date/region filters or result-count control), which agents can work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources