Skip to directory

About Search1API MCP

Official Search1API MCP server for multi-engine web search, news, webpage crawling, sitemap discovery, trending topics, and search result rendering.

What you can use it for

  • web search
  • news search
  • web page crawling
  • sitemap discovery
  • trending topics
  • agent research
Connection and setup
Hosting
Remote hosted service
Transport
streamable-http
Endpoint
https://mcp.search1api.com/mcp
Authentication
Authentication is required. OAuth 2.1 with offline_access is the recommended method; a Bearer API key is an alternative and is optional when OAuth is used.

Requirements

  • An MCP client supporting remote Streamable HTTP and OAuth 2.1, or the documented Bearer API-key mode.
  • A Search1API account; tool usage consumes account credits.

Setup steps

  1. In the MCP client, add a remote Streamable HTTP MCP server using https://mcp.search1api.com/mcp.
  2. Complete the client browser OAuth flow and approve Search1API access. The discovered OAuth scope is offline_access.
  3. For clients using an API key instead, open https://dashboard.search1api.com/ (it redirects to the Search1API app), choose API Keys, create a key, and configure it as an Authorization: Bearer value in the client secret/header facility. Never place the key in a public catalog or chat.
  4. Reconnect the server and confirm initialize/tools/list succeeds. A harmless search query can check function, but may consume credits; check the dashboard balance first.
Tools 7+

README documents these tool names, but no authenticated tools/list was performed; inventory is not marked exact.

  • search

    Search the web through a selected search service and return citable results.

    Parameters: query, max_results, search_service, page, crawl_results, include_sites, exclude_sites, time_range
    01
  • news

    Search for news articles through a selected news service.

    Parameters: query, max_results, search_service, crawl_results, include_sites, exclude_sites, time_range
    02
  • crawl

    Extract page content from a URL.

    Parameters: url
    03
  • sitemap

    Find related links for a URL.

    Parameters: url
    04
  • trending

    Retrieve trending topics from a supported platform.

    Parameters: search_service, max_results
    05
  • ask

    Run agentic search that selects search engines and returns citable results; repository documentation says this request uses five credits.

    Parameters: query
    06
  • render_results

    Render already retrieved result cards in clients that support MCP Apps; this does not repeat the search.

    07

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

Limitations and notes
  • The remote server requires authentication before capability discovery.
  • Search/crawl operations consume service credits; the README documents five credits for ask requests. Review the live dashboard for current plans and balances.
  • The MCP.Directory profile linked github.com/fatwang2/search1api-mcp; GitHub redirects that URL to superagents-lab/search1api-mcp, the current repository that identifies this as the official server.
Source discrepancies
  • The saved MCP.Directory profile repository URL redirects from https://github.com/fatwang2/search1api-mcp to https://github.com/superagents-lab/search1api-mcp; current publisher ownership is recorded from the redirected repository and Search1API product site.
Original sources
  • Official publisher repository README

    Identifies this as Search1API's official MCP server; documents OAuth 2.1 and API-key modes, remote endpoint, stdio package, tool names/parameters, credit caveats, and product icon.

  • Official product website

    Confirms Search1API product identity and its web search/crawl capabilities; linked from the official server README.

  • Official API-key dashboard linked by publisher

    Official dashboard page lists an API Keys section for creating and managing keys; currently redirects to app.s1.dev.

  • Official OAuth protected-resource metadata

    Live metadata identifies the MCP resource, authorization server https://clerk.s1.dev, and supported scope offline_access.

  • Official Streamable HTTP endpoint

    Unauthenticated initialize returned HTTP 401 with a Bearer OAuth resource-metadata challenge and the message that OAuth 2.1 or a Search1API API key is required. Reachability/auth challenge verified; MCP initialization and tools/list remain blocked pending authentication.

  • Official MCP product icon

    Downloaded HTTP 200 image/png; decoded as 512x512 PNG and visually reviewed on light and dark backgrounds.

  • Official MCP server metadata

    The publisher metadata declares the remote endpoint https://mcp.search1api.com/mcp with transport type streamable-http.

  • official tool documentation

    Official README documents seven tools: search, news, ask, crawl, sitemap, trending, render_results.

Documentation checked 2026-10-28T00:00:00Z. Connection has not been runtime tested.