SearchStack
dev.searchstackPublished by searchstack.devOfficial publisherv1.0.1Updated Oct 24, 2026
Agent-driven search: build, import, tune, search, and score result quality — all over MCP.
Overview
Lets an assistant build, import, tune, and search a search index, and score the quality of its results, over MCP.
- What you can do
- SearchStack is a remote MCP endpoint for agent-driven search work. According to its registry description, it lets an assistant build and import search indexes, tune search configuration, run searches, and score result quality. The manifest lists no individual tools, so the exact tool set is not documented here.
- When to use it
- Worth considering when an assistant needs to set up or adjust a search index and evaluate how good its results are, rather than only issuing one-off queries. It is a hosted endpoint, so nothing is installed locally.
- Requirements
- A remote MCP client that supports streamable HTTP, connecting to the provider's hosted endpoint. The manifest declares an X-API-Key header, so an API key from the provider is likely required even though authentication is not declared. No packages, environment variables, or local runtime are listed.
Installation
In SourceWeft
- Open SearchStack in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/dev.searchstack%2Fsearchstack/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"searchstack": {
"type": "http",
"url": "https://mcp.searchstack.dev/"
}
}
}Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.