SSearch
REMOTE · API.SSEARCH.CC · SCANNED SEP 20
Independent web search index for AI agents. Fast structured results via MCP and API.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 177 tokens (~44/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the SSearch MCP server?
SSearch is a hosted endpoint at https://api.ssearch.cc/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.ssearch.cc
claude mcp add --transport http cc-ssearch-search 'https://api.ssearch.cc/mcp'
{
"mcpServers": {
"cc-ssearch-search": {
"url": "https://api.ssearch.cc/mcp"
}
}
} {
"servers": {
"cc-ssearch-search": {
"type": "http",
"url": "https://api.ssearch.cc/mcp"
}
}
} [mcp_servers.cc-ssearch-search] url = "https://api.ssearch.cc/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cc-ssearch-search": {
"type": "remote",
"url": "https://api.ssearch.cc/mcp",
"enabled": true
}
}
} openclaw mcp add cc-ssearch-search --url 'https://api.ssearch.cc/mcp' --transport streamable-http
mcp_servers:
cc-ssearch-search:
url: "https://api.ssearch.cc/mcp" {
"McpServers": {
"cc-ssearch-search": {
"Transport": "http",
"Url": "https://api.ssearch.cc/mcp"
}
}
} assistant mcp add cc-ssearch-search -t streamable-http -u 'https://api.ssearch.cc/mcp'
{
"mcpServers": {
"cc-ssearch-search": {
"type": "http",
"url": "https://api.ssearch.cc/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search_plan” rewrote its description, which is the text the model reads security
- Tool “search_sources” rewrote its description, which is the text the model reads security
- Tool “search_web” rewrote its description, which is the text the model reads security
- 18 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Sept 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.ssearch.cc/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.ssearch.cc | CN=YE2,O=Let's Encrypt,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6a1151f3f2f2627a5b91cf947651b4e6429 |
| SANs: api.ssearch.cc | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.ssearch.cc. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cc. | present | 12593 | 13 | Verified |
| ssearch.cc. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.ssearch.cc/mcp | Verified | 200 | |
| http (plaintext) | http://api.ssearch.cc/mcp | HTTPS enforced | 308 | https://api.ssearch.cc/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fetch_page ~46
Fetch and extract readable page text; optionally fall back to Common Crawl.
| Name | Type | Req | Description |
|---|---|---|---|
| archive_fallback | boolean | – | – |
| max_chars | integer | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
search_plan ~25
Show the normalized local search plan for a query.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
search_sources ~19
Describe the local SSearch corpus and search backends.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_web ~46
Search the SSearch ingested corpus and return a small reranked candidate set.
| Name | Type | Req | Description |
|---|---|---|---|
| fresh | boolean | – | – |
| max_results | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
What is the SSearch MCP server?
SSearch is an MCP server listed in the public MCP registry as cc.ssearch/search. Independent web search index for AI agents. Fast structured results via MCP and API. This page covers its hosted endpoint (https://api.ssearch.cc/mcp).
Is the SSearch MCP server safe to use?
SSearch scores 61 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the SSearch MCP server expose?
SSearch exposes 4 tools: search_web, fetch_page, search_plan, search_sources. Their descriptions and schemas cost roughly 136 tokens of context every time the server is loaded.
Does the SSearch MCP server require authentication?
No. We connected to SSearch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SSearch MCP server still maintained?
SSearch is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.