mcpbeat

Search1API MCP Server

io.github.superagents-lab/search1api
answering

Search1API is answering right now. Last checked 8 min ago. 1 363 installs a week from npm. Last commit 2 Aug 2026.

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

Installs per day peak 416 · avg 70 · +174% w/w
a month agotoday
Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
28 ms
Response time
average over 24h
1 363
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add search1api --transport http https://mcp.search1api.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "search1api": {
      "url": "https://mcp.search1api.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.search1api]
url = "https://mcp.search1api.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "search1api": {
      "url": "https://mcp.search1api.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "search1api": {
      "url": "https://mcp.search1api.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://mcp.search1api.com/mcp streamable-http needs key 52 ms 8 min ago

Search1API — questions

Answers built from our own checks of this server.

Why is there no tool list for Search1API?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Search1API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 28 ms. The bar chart above shows every period we have measured.
How do I connect Search1API?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does Search1API need an API key?
Yes. Every time we knock, Search1API answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Search1API?
It answers our handshake in 28 ms on average, which is faster than 99% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Search1API?
The npm package search1api-mcp was installed 1 363 times in the last week. Week over week that is +174%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Search1API open source?
Yes — it is published under the MIT licence, written in TypeScript and 173 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.