mcpbeat Sign in

SSearch MCP Server

answering

SSearch is answering right now. Last checked 14 min ago. It exposes 4 tools.

Web search for AI agents using SSearch's independent search infrastructure.

Uptime history 9 hours of history
9 hours agonow
100.0%
Uptime 24h
30 of 30 checks
4
Tools
read from the server
875 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check SSearch every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

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

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

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

page
fetch_page
Fetch and extract readable page text; optionally fall back to Common Crawl.
plan
search_plan
Show the three external sources and cleaned query that would be used.
sources
search_sources
List local and external search sources.
web
search_web
Search the local/open web index and return a small reranked candidate set.

Endpoints

URLTransportStateLatencyChecked
https://api.ssearch.cc/mcp streamable-http answering 1291 ms 14 min ago

Alternatives to SSearch

same job, measured the same way
WonderCal
by digital-wisdom-ai

Scheduling infrastructure for AI agents across Google and Microsoft calendars.

answering
срезAI — Search API for AI agents
by srezai

Web search, page reading and structured extraction for AI agents, with strong RU coverage

10 tools answering
SearchForge
by divyanshu-iitian

Free open-source web search and page reading for LLMs, AI agents, and RAG.

local only
Brave Search
by pipeworx-io

Brave Search MCP — independent web index (no Google/Bing dependency)

33 tools answering
Parallel Search MCP
by parallel

The best web search for your AI Agent

answering
Tavily MCP
by tavily-ai

MCP server for advanced web search using Tavily

15 779 installs/wk local only
L402 Search MCP
by llmops-pro

No-KYC web search for AI agents, paid per query in Lightning sats (L402). Holds no keys.

24 installs/wk local only
MESSORA
by messora

Scrape, crawl and search the web for AI agents via MCP.

5 tools answering

SSearch — questions

Answers built from our own checks of this server.

What can SSearch do?
It exposes 4 tools, read directly from the server on our last check. Among them: fetch_page, search_plan, search_sources, search_web. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is SSearch working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 30 of 30 checks got a reply (100.0%), average response time 875 ms. The bar chart above shows every period we have measured.
How do I connect SSearch?
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.
Does SSearch need an API key?
No. SSearch completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is SSearch?
It answers our handshake in 875 ms on average, which is faster than 14% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.