Skip to main content
Glama
zuozh11

grok-native-search-mcp

by zuozh11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to grok-native-search-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-web-search

      tolstikov-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables web search, page fetching and cleaning, OCR from images, and broken-link checking through MCP tools, with multi-provider aggregation, caching, and anti-detection features.
      50 npm
      MIT

    • Ollama Web Search

      deXterbed
      A
      license
      A
      quality
      B
      maintenance
      Enables web search and web fetch operations using Ollama's hosted APIs, allowing MCP clients to search the web and retrieve page content.
      2
      MIT

    • web-search-mcp

      hbhszy
      A
      license
      A
      quality
      D
      maintenance
      Enables real-time web search via DeepSeek's search-enhanced dialogue, providing search results as answers through MCP tools.
      1
      MIT

    • grok-build-plugin

      VasiHemanth
      A
      license
      Not graded
      quality
      B
      maintenance
      Live X (Twitter) and web search for any coding agent through your existing Grok subscription. Exposes a grok_search MCP tool, so no X API key or X developer account is needed.
      38 npm
      30
      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.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: web_search for general web discovery, x_search specifically for X content, and web_fetch for retrieving a known URL. The descriptions explicitly cross-reference each other (e.g., web_search notes 'For X-only content use x_search'), leaving no ambiguity about which tool to select.

    Naming Consistency5/5

    All three tool names follow a consistent `[source]_[action]` pattern: web_search, x_search, web_fetch. The naming convention is uniform, predictable, and immediately conveys scope (web vs. x) and operation (search vs. fetch).

    Tool Count5/5

    With only 3 tools, the server is tightly scoped for its purpose: general web search, X-specific search, and URL fetching. This is well within the ideal 3–15 range and every tool earns its place; adding more would likely introduce redundancy.

    Completeness5/5

    The surface covers the full lifecycle of a search task: discover sources (web_search, x_search) and then retrieve/verify content (web_fetch). The tools explicitly reference each other to create a complete workflow, with no obvious gaps for the stated domain.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources