Skip to main content
Glama
wtznicy

MyWebSearch

by wtznicy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to MyWebSearch

No user-submitted related servers found.

    Related Servers

    • web-mcp

      Chang-Tong
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for multi-engine web search and web page fetching, supporting parallel search, content extraction, and optional LLM-powered search summarization and deep search.
      5
      MIT

    • grok-mcp

      dq52099
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server providing web search, news search, and X/Twitter search capabilities via HTTP or stdio.
      -

    • searxng-mcp

      88plug
      F
      license
      A
      quality
      A
      maintenance
      An MCP server for SearXNG that provides web search capabilities with concise model-visible output while preserving full result payloads in metadata. It supports search, parallel fetching, URL extraction, and research workflows through both local stdio and streamable HTTP transports.
      7
      4
      -

    • web-docs-mcp

      Aleksandrr
      F
      license
      A
      quality
      B
      maintenance
      A local-first MCP server for web search and documentation fetching, providing free DuckDuckGo search, URL-to-markdown conversion, and library docs from npm, PyPI, crates.io, Go, and GitHub with caching.
      5
      -

    • agent-tools

      garnetlyx
      A
      license
      Not graded
      quality
      C
      maintenance
      A multi-function Streamable HTTP MCP tool aggregation server that provides web search via Brave, Exa, and SearXNG with multi-key rotation and cross-provider fallback, and supports extensible tool families (URL fetch, code search, RAG) through a pluggable architecture.
      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/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a well-defined target: search vs. generic fetching vs. site-specific fetching vs. official docs. The specialized fetchers explicitly delegate non-matching URLs to fetchWebContent, reducing misselection.

    Naming Consistency4/5

    Most tools follow a verb-first camelCase pattern (fetchX, queryDocs, resolveLibraryId). 'search' is a bare verb without an object, and object specificity varies, but the pattern remains predictable.

    Tool Count5/5

    Seven tools cover the server's purpose without redundancy or bloat. The count is within the ideal 3–15 range and each tool contributes a distinct capability.

    Completeness5/5

    The set covers generic web fetching, specialized extraction for CSDN, Juejin, and GitHub READMEs, multi-engine web search, and official documentation lookups. No critical functionality appears missing for a web search and content-fetch server.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources