Is the Ssearch Search MCP server down?

mcp-registry/cc.ssearch/search · v0.2.0

As of 2026-10-24 22:22 UTC, the Ssearch Search MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 8 outages in 90 days, with a median recovery of 13 minutes.

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

claude mcp add --transport http ssearch-search-mcp-server https://api.ssearch.cc/mcp

{
  "mcpServers": {
    "ssearch-search-mcp-server": {
      "type": "http",
      "url": "https://api.ssearch.cc/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (71/100)

What to fix (3)

Auto-fix: 7 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 7 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcc.ssearch%2Fsearch/fixes

{
  "name": "fetch_page",
  "description": "Fetch and extract readable page text; optionally fall back to Common Crawl.",
  "inputSchema": {
    "type": "object",
    "title": "fetch_pageArguments",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "title": "Url"
      },
      "max_chars": {
        "type": "integer",
        "title": "Max Chars",
        "default": 30000
      },
      "archive_fallback": {
        "type": "boolean",
        "title": "Archive Fallback",
        "default": true
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_context",
  "description": "Retrieve only the stored passages in a search result that are relevant to the information you need.",
  "inputSchema": {
    "type": "object",
    "title": "get_contextArguments",
    "required": [
      "document_id",
      "query"
    ],
    "properties": {
      "query": {
        "type": "string",
        "title": "Query"
      },
      "max_chars": {
        "type": "integer",
        "title": "Max Chars",
        "default": 5000
      },
      "document_id": {
        "type": "string",
        "title": "Document Id"
      },
      "max_passages": {
        "type": "integer",
        "title": "Max Passages",
        "default": 5
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_document",
  "description": "Retrieve the broader stored text for a known SSearch document ID.",
  "inputSchema": {
    "type": "object",
    "title": "get_documentArguments",
    "required": [
      "document_id"
    ],
    "properties": {
      "max_chars": {
        "type": "integer",
        "title": "Max Chars",
        "default": 30000
      },
      "document_id": {
        "type": "string",
        "title": "Document Id"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/cc.ssearch/search"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/cc.ssearch/search"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~796 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.71% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• search_web ~140 tokens
• get_context ~134 tokens
• search_documents ~118 tokens
• fetch_page ~110 tokens
• get_document ~93 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcc.ssearch%2Fsearch.svg)](https://glimind.com/server/mcp-registry%2Fcc.ssearch%2Fsearch?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fcc.ssearch%2Fsearch?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcc.ssearch%2Fsearch.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcc.ssearch%2Fsearch.svg
   :target: https://glimind.com/server/mcp-registry%2Fcc.ssearch%2Fsearch?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:6753b3254887578a…, first seen 2026-10-17, included at leaf 5977 of 61,774. Version history · verify what your client received.

Tools (8)

• fetch_page
• forward_canary
• get_context
• get_document
• search_documents
• search_plan
• search_sources
• search_web

Compare: most reliable web servers · most reliable other servers · most reliable retrieval servers · most reliable search servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Ssearch Search MCP server down right now?

As of 2026-10-24 22:22 UTC, the Ssearch Search MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 8 outages in 90 days, with a median recovery of 13 minutes.

How many tools does Ssearch Search MCP server provide?

Ssearch Search MCP server advertises 8 tools, including fetch_page, forward_canary, get_context, get_document, search_documents.

How do I install Ssearch Search MCP server?

Point your MCP client at this streamable-http endpoint: https://api.ssearch.cc/mcp

Is the Ssearch Search MCP server safe to connect to an AI agent?

Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Ssearch Search MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.