mcp-registry/dev.searchstack/searchstack · v1.0.0.0
As of 2026-10-19 08:17 UTC, the Searchstack MCP server is up (it requires sign-in) with a Glimind reliability score of 78/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 minutes.
Agent-driven search: build, import, tune, search, and score result quality — all over MCP.
Claude Code
claude mcp add --transport http searchstack-mcp-server https://mcp.searchstack.dev
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"searchstack-mcp-server": {
"type": "http",
"url": "https://mcp.searchstack.dev"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
107 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
4 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
2 tool(s) have descriptions under 20 characters.
Say when to use the tool and what it returns, not just its name restated ("Get weather" → "Current weather for a city: temperature, conditions, wind. Use for 'now', not forecasts."). How to fix →
Loading this server's tool list costs an agent ~23,346 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Requires authentication (Bearer); tool definitions could not be read anonymously.
If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.
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/dev.searchstack/searchstack"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/dev.searchstack/searchstack"}) over MCP.
group_search_post ~721 tokenssearch_list_post ~689 tokensgroup_search ~593 tokenssearch_group_by_image_base64_post ~587 tokenssearch_group_by_image_post ~564 tokensStatic 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:
[](https://glimind.com/server/mcp-registry%2Fdev.searchstack%2Fsearchstack?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fdev.searchstack%2Fsearchstack?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.searchstack%2Fsearchstack.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.searchstack%2Fsearchstack.svg :target: https://glimind.com/server/mcp-registry%2Fdev.searchstack%2Fsearchstack?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:62fa8d96f5dbcc76…, first seen 2026-10-17, included at leaf 12921 of 25,755. Version history · verify what your client received.
Compare: most reliable other servers · most reliable analytics servers · most reliable security servers · most reliable data servers · most reliable ml servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-19 08:17 UTC, the Searchstack MCP server is up (it requires sign-in) with a Glimind reliability score of 78/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 minutes.
Searchstack MCP server advertises 107 tools, including account_get, account_get_name, analytics_get_group, analytics_get_list, api_key_create_read_only.
Point your MCP client at this streamable-http endpoint: https://mcp.searchstack.dev
Glimind scanned all 107 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.
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.