mcpbeat Sign in

SSearch MCP Server

by ssearch Your server? Claim it
answering

SSearch is answering right now. Last checked 2 min ago. It exposes 8 tools.

Free web search for AI agents. No API key required. Hosted MCP in active development.

Uptime history 47 days of history · worst day 0%
47 days agonow
100.0%
Uptime 24h
92 of 92 checks
8
Tools
read from the server
419 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 10

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 18 September 2026. No other catalogue keeps this.

1 Oct a tool appeared forward_canary
20 Sep 3 tools appeared get_context, get_document, search_documents
20 Sep a tool description was rewritten search_web
20 Sep a tool changed the parameters it asks for search_web
20 Sep a tool changed version
18 Sep 3 tool descriptions were rewritten search_plan, search_sources, search_web

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 2 min ago.

run in your terminal
claude mcp add search --transport http https://api.ssearch.cc/mcp
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "search": {
      "type": "http",
      "url": "https://api.ssearch.cc/mcp"
    }
  }
}

Available tools 8

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

context
get_context
Retrieve only the stored passages in a search result that are relevant to the information you need.
document
get_document
Retrieve the broader stored text for a known SSearch document ID.
documents
search_documents
Search SSearch-owned stored full-text documents. Successful misses can be promoted into the live index.
forward
forward_canary
Dev-only transport proof. Forward a fake canary transiently and return only delivery status. Never use a real credential.
page
fetch_page
Fetch and extract readable page text; optionally fall back to Common Crawl.
plan
search_plan
Show the normalized local search plan for a query.
sources
search_sources
Describe the local SSearch corpus and search backends.
web
search_web
Search SSearch. Set wait_for_coverage to search owned documents and, only if needed, external discovery on a miss.

Endpoints

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

Alternatives to SSearch

same job, measured the same way
Bing Search (Free)
by iridite

Free Bing search MCP server - No API key required

84 installs/wk local only
Deep Research MCP Server
by perufitlife

Web search, clean page reading & one-call research dossiers for AI agents. No API key.

78 installs/wk local only
AgentSearch (agentsearchhq.com)
by agentsearchhq-coder

AgentSearch web search for agents: free, no API key (25/day per IP). Paid extract $0.005 via x402.

596 installs/wk local only
Web Search
by hec-ovi

Keyless multi-engine web search, fetch, and clean-Markdown read for AI agents. No API keys.

115 installs/wk local only
Search Memory
by kefyusuf

Free web search and long-term memory for AI assistants. No API keys; data stays local.

561 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.

53 installs/wk local only
Webshift
by x-hannibal

Rust MCP server for denoised web search — fetch, clean, and rerank web content for AI agents.

local only
Webshift
by x-monk

Rust MCP server for denoised web search — fetch, clean, and rerank web content for AI agents.

local only

SSearch — questions

Answers built from our own checks of this server.

What can SSearch do?
It exposes 8 tools, read directly from the server on our last check. Among them: fetch_page, forward_canary, get_context, get_document, search_documents, search_plan and 2 more. 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 92 of 92 checks got a reply (100.0%), average response time 419 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 in the form 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 8 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 419 ms on average, which is faster than 31% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.