Skip to main content
Glama
anaconda110

ollama-search-mcp

by anaconda110
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to ollama-search-mcp

No user-submitted related servers found.

    Related Servers

    • ollama-cloud-mcp

      bouroo
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to search the web and fetch individual pages through two stdio tools, returning ranked results or extracted page content, titles and outbound links. It wraps a hosted, API-key-authenticated service (or a local daemon) with zero runtime dependencies.
      14 npm
      MIT

    • Oxylabs Web API MCP Server

      thevastas
      A
      license
      A
      quality
      C
      maintenance
      Gives MCP-capable agents live web access: search the web, scrape pages into Markdown (including JavaScript-heavy and bot-protected sites), and extract named fields as JSON, with job polling, token-aware content offloading, and built-in research guidance. Ships as a self-hostable stdio or HTTP service with spend caps and per-request key support.
      7
      MIT

    • jev-search-mcp

      mukiwu
      A
      license
      A
      quality
      B
      maintenance
      Enables plain-language web search with automatic source and time-window selection, returning relevance-ranked links and summaries to MCP clients such as Claude Code and Codex. Works as an MCP server, CLI, and Claude Code plugin with zero runtime dependencies.
      1
      7
      MIT

    • searxng-mcp

      TadMSTR
      A
      license
      A
      quality
      C
      maintenance
      MCP server for private web search via self-hosted SearXNG with local reranking, full-page content fetching via Firecrawl, and optional Ollama-powered query expansion and summaries.
      7
      222 npm
      25
      MIT
    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.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    web_search and web_fetch have clearly distinct, complementary roles: one discovers ranked results, the other reads a single page. The descriptions explicitly frame fetch as the follow-up to search, so an agent can never confuse them.

    Naming Consistency5/5

    Both tools follow the same snake_case verb_noun pattern with a shared 'web_' prefix (web_search, web_fetch). The convention is perfectly predictable.

    Tool Count3/5

    Two tools is thin for a standalone server, though each earns its place as a search/read pair. It sits at the borderline of the rubric's 1-2 tool range rather than being clearly well-scoped.

    Completeness5/5

    For the stated purpose of live web access, the discover-then-read loop is fully covered with no dead ends. There is no obvious missing operation an agent would need for this domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources