MCP.so
Sign In

Search1API MCP Server

@SuperAgents, LLC

Basic information

Transport

stdio

Authentication

OAuth

Category

Search

Author

SuperAgents, LLC

Submitted by

王顶

About Search1API MCP Server

Web search, agentic search, news, page retrieval, sitemaps, and trending topics through Search1API.

#search1api#web-search#agentic-search#news#crawl#sitemap#trending#remote-mcp#oauth

Connection details

https://mcp.search1api.com/mcp

Setup

claude mcp add search1api --transport http https://mcp.search1api.com/mcp

Search1API MCP Server tools

7

Search the live public web when the user needs current information, sources, or research. Returns citable results with id, title, URL, and text. Each result includes a URL that can be read in full.

Search current news when the user asks about recent events, announcements, or coverage. Returns citable article results with title, URL, snippet, and optional extracted text.

Extract the readable title and full text from a public URL supplied by the user or returned by search.

Discover related public links from a page or domain when the user wants to explore a site's structure or available pages.

List currently trending repositories or stories from GitHub or Hacker News when the user asks what is popular now.

Describe what you are looking for in natural language when you do not know which source to search. Search1API picks up to five engines (web, Hacker News, Reddit, GitHub, X, arXiv, Wikipedia, and more), infers a time window from phrases such as "this week", and returns at most 10 relevant results ranked by relevance. Costs 5 credits; use search when you already know the engine.

Present already retrieved source results as source cards when the host supports UI, with a complete readable text list otherwise. Use when the user wants to browse sources or a visual list helps the task. Pass existing results in the desired order; never invent source URLs or factual titles. Does not search, crawl, fetch URLs, verify sources, or consume search credits. Do not call for intermediate research results or when a text answer is sufficient.

Overview

What is Search1API?

Search1API is the official MCP server for Search1API: web search across many engines, agentic search, news, full-page retrieval, sitemap discovery, and GitHub / Hacker News trending in one server. It runs as a hosted Remote MCP server at https://mcp.search1api.com/mcp with OAuth sign-in, so there is nothing to install.

How to use Search1API?

  • Claude.ai / Claude Desktop: install Search1API from the Claude directory, click Connect, and sign in with your Search1API account.
  • Any OAuth-aware MCP client (Claude Code, Cursor, VS Code, Windsurf, ...): add the remote URL https://mcp.search1api.com/mcp and sign in when prompted. Clients without OAuth can send Authorization: Bearer YOUR_SEARCH1API_KEY instead (key from the dashboard).
  • Local stdio (optional): npx -y search1api-mcp with the SEARCH1API_KEY environment variable (Node.js 20+).

Claude Code example:

claude mcp add --transport http search1api https://mcp.search1api.com/mcp

Key features

  • search: Google, Bing, DuckDuckGo, Yahoo, Yandex, and specialized sources including GitHub, Reddit, X, arXiv, Wikipedia, Grokipedia, YouTube, WeChat, Bilibili, and IMDb, with site filters, time ranges, and pagination
  • ask: agentic search that picks engines and a time window from a natural-language request and returns up to 10 relevant, citable results
  • news: news search, including Hacker News with points and comment counts
  • crawl: full content of any URL
  • sitemap: related links discovered from a URL
  • trending: GitHub and Hacker News trends
  • render_results: shows selected results as interactive source cards in MCP Apps clients (a readable list elsewhere), without repeating a search or using credits
  • Results carry source URLs for citation

Use cases

  • Give your assistant real-time web and news search with citable sources
  • Compare findings across engines and specialized sources
  • Read and summarize full pages from search results
  • Track trending GitHub repositories and Hacker News stories

Frequently asked questions

1

Do I need an API key?

Not for OAuth clients: connect to the remote URL and sign in with your Search1API account. For header-based or local stdio setups, get a key from the [Search1API dashboard](https://dashboard.search1api.com).

2

Which clients are supported?

Any client that speaks Streamable HTTP MCP, including Claude, Claude Code, Cursor, VS Code, and Windsurf. Local stdio is available through the `search1api-mcp` npm package.

3

Where are the docs and source?

Docs: [s1.dev/docs/integrations/mcp](https://s1.dev/docs/integrations/mcp). Source (MIT): [github.com/superagents-lab/search1api-mcp](https://github.com/superagents-lab/search1api-mcp). Updates: [@search1api_dev](https://x.com/search1api_dev) on X.

4

What is the Search1API remote MCP server?

The Search1API remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.search1api.com/mcp, so AI assistants can connect to it without installing or running anything locally.

5

How do I connect to the Search1API MCP server?

Add the endpoint https://mcp.search1api.com/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

6

Does the Search1API MCP server require authentication?

Yes. Search1API uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.

7

Which transport does the Search1API MCP server use?

Search1API exposes a stdio endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments