Skip to main content
Glama
Sign In
Search1API MCP Server

Search1API MCP Server

by superagents-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Search1API MCP Server

No user-submitted related servers found.

    Related Servers

    • WebSearch-MCP

      mnhlt
      A
      license
      B
      quality
      C
      maintenance
      A Model Context Protocol server that enables AI assistants to perform real-time web searches, retrieving up-to-date information from the internet via a Crawler API.
      1
      70 npm
      42
      ISC

    • Firecrawl MCP Server

      firecrawl
      A
      license
      A
      quality
      B
      maintenance
      Firecrawl, the context API for AI agents, as an MCP server. Search the web, scrape any URL, parse PDFs and documents, crawl and map sites, interact with pages in a real browser, run Agent research jobs, monitor pages for changes, and search scientific papers. Returns clean Markdown or structured JSON. Run locally with npx firecrawl-mcp or connect to https://mcp.firecrawl.dev/v2/mcp
      28
      158,347 npm
      7,764
      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.1/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct roles: sitemap vs crawl vs deepcrawl are well-separated by scope, and maps/news/trending target specific sources. The main overlap is between search, ask, and news — all return web-ish results — though the descriptions (single engine vs multi-engine vs news) give an agent enough to choose correctly.

    Naming Consistency3/5

    Naming mixes bare nouns (sitemap, maps, news, trending), bare verbs (search, ask, crawl), verb_noun (send_feedback, render_results), and a compound (deepcrawl). Each name is readable and none are cryptic, but there is no single predictable pattern an agent can rely on.

    Tool Count5/5

    Ten tools is well-scoped for a search-and-retrieval server, with each tool covering a distinct retrieval mode or utility. Nothing feels padded or missing at the count level.

    Completeness4/5

    The surface covers the full research lifecycle: discovery (sitemap, trending, news, maps), search (search, ask), and reading (crawl, deepcrawl), plus presentation and feedback utilities. Minor gaps exist — no structured extraction or batch URL fetch — but core workflows have no dead ends.

    Maintenance

    ActivityActive
    ResponsivenessSyncing

    Resources