Log inSubmit server
Search1API logo

Search1API

Search1API provides web and news search, URL crawling, sitemaps, and GitHub or Hacker News trends through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Search1API

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "search1api": {
      "command": "npx",
      "args": [
        "-y",
        "search1api-mcp"
      ],
      "env": {
        "SEARCH1API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 7 tools correctly (7d ago).

Overview

Search1API MCP server connects MCP clients to Search1API for web search, news lookup, page extraction, sitemap discovery, and trending topics. It runs remotely over Streamable HTTP or locally through Node.js and npx, with OAuth or an API key for authentication. Search results can be crawled for full content, and returned results include citable IDs, titles, and URLs. Reach for it when an agent needs current web information, article content, site links, or developer-focused trends.

Use cases

  • Search the web for current technical information
  • Find and retrieve recent news articles
  • Crawl a search result for full page content
  • Discover links in a website sitemap
  • Track GitHub and Hacker News trends

Key features

  • Web search across multiple providers
  • News search with time and site filters
  • URL content extraction
  • Sitemap link discovery
  • GitHub and Hacker News trends
  • Remote OAuth and local API-key authentication

Tools7

What Search1API lets your agent do. Expand a tool for its parameters.

Verified live~1.5k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

7/7 checks healthy over the last 39d

What it can do

From the 7 tools this server returned when we ran it; 7 declare their own safety hints.

Makes network requests · 7Read-only tools · 7
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age688 days
Maintainers1

Observed 2026-10-15 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · search1api-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars173Stargazers on the source repository.
npm downloads1.9kPackage downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed7Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Search1API works

What Search1API MCP server does

Search1API MCP server exposes Search1API’s search and extraction API through MCP. It gives agents tools for general web search, news discovery, URL crawling, sitemap retrieval, and trend lookup. Search results contain an ID, title, and URL structure that can be cited or passed to the crawl tool for fuller page content.

The search tool supports multiple backends, including Google, Bing, DuckDuckGo, Yahoo, X, Reddit, GitHub, YouTube, arXiv, WeChat, Bilibili, IMDb, and Wikipedia. News searches can use Google, Bing, DuckDuckGo, Yahoo, or Hacker News. Trending results are available for GitHub and Hacker News.

How it works

The hosted endpoint is available at https://mcp.search1api.com/mcp and uses Streamable HTTP. OAuth-capable clients can connect without an API key and complete sign-in in a browser. Clients that use bearer credentials can send a Search1API key in the Authorization header. A legacy query-string key is also supported, although the documentation warns that URL credentials can appear in logs, shell history, or other exposed locations.

A local stdio deployment uses Node.js 20 or later and runs the package with npx, so cloning the repository is not required. Each request needs authentication, including MCP discovery requests such as initialization and tool listing. The hosted service also publishes a static server card for pre-connection inspection.

Setup and configuration

For a remote connection, configure the MCP URL in the client and choose OAuth or an API key. The README provides configurations for Claude Desktop, Claude.ai, Cursor, VS Code, Claude Code, and Windsurf. Cursor users can install the included remote-MCP plugin or configure the endpoint manually.

For local mode, run npx -y search1api-mcp with SEARCH1API_KEY in the process environment. Self-hosted HTTP deployments behind a proxy can set MCP_ALLOWED_HOSTS to a comma-separated list of internal hostnames. Browser clients that send an Origin header may also require trusted hostnames in MCP_ALLOWED_ORIGINS; server-side clients normally omit that header.

Tools and capabilities

The Search1API MCP server provides five tools:

  • search accepts a query, result limit, search service, site inclusion or exclusion lists, and day, month, or year time ranges. It can optionally crawl top results.
  • news searches articles with similar filtering and optional crawling controls.
  • crawl extracts content from a specified URL.
  • sitemap returns related links from a specified URL.
  • trending returns popular topics from GitHub or Hacker News.

Search and news requests start at one credit. Each successful result crawl adds one credit to that request. The default result limit for search, news, and trending is 10, while search uses Google and news uses Bing by default.

Limitations and notes

The service depends on Search1API credentials or OAuth access, and unauthenticated requests receive an authentication challenge. Query-parameter authentication is available for compatibility but is less appropriate when URLs may be recorded. The available search providers and trend sources are limited to the services listed for each tool. Page extraction requires a URL, and sitemap discovery also operates on a supplied URL rather than an arbitrary search query.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Search1API

Search1API is an MCP server that connects AI clients to the Search1API web data service. Its main tools search the web and news, crawl URLs, retrieve sitemap links, and return trending topics from GitHub or Hacker News. It supports remote Streamable HTTP connections and local stdio use with OAuth or an API key.

Use the hosted MCP URL without installing software, or run the local package with Node.js 20 or newer and npx. Local clients can start `npx -y search1api-mcp` and provide `SEARCH1API_KEY` in the environment. The repository also documents client-specific remote configurations.

Yes, Search1API works with Cursor through its included remote-MCP plugin or a manual MCP configuration. Install the plugin from the documented Cursor locations and sign in when prompted, or set the hosted URL and bearer authorization header directly.

Authenticate with OAuth 2.1, a bearer API key, or the legacy `apiKey` URL parameter. OAuth clients connect to the remote endpoint and complete browser sign-in. API-key clients can send `Authorization: Bearer YOUR_SEARCH1API_KEY`; the documentation recommends OAuth or the header over query parameters.

Search1API supports Google, Bing, DuckDuckGo, Yahoo, X, Reddit, GitHub, YouTube, arXiv, WeChat, Bilibili, IMDb, and Wikipedia for web search. News supports Google, Bing, DuckDuckGo, Yahoo, and Hacker News, while trending supports GitHub and Hacker News.

Related MCP servers

All in Search & Data Extraction All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSearch1API AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/search1api?style=directory)](https://allmcps.com/mcp/search1api)
HTML Embed
<a href="https://allmcps.com/mcp/search1api"><img src="https://allmcps.com/api/badge/search1api?style=directory" alt="Search1API on AllMCPs" /></a>