Search remote MCP servers
search_serversUse when the user needs an MCP server for a task, or asks whether one exists, works today, or needs a key or sign-in. Do not use for general web search; for one server already known by name use get_server. Find remote MCP servers listed in the Official MCP Registry, with MCP Station's daily measurements. Turn the user's need into words (q) plus filters. Example: 'crypto market data, no API key, working' -> q='crypto market data', auth='none', reachable=true. Results are ordered by relevance first, then by published rank rules (measurements only, no paid placement). similar_to='' returns other working servers in the same categories with the same authentication.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "search_servers"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Words, max 200 characters | |
| auth | No | Authentication at the last check | |
| risk | No | Declared by the server's tool hints | |
| limit | No | Ask only for as many results as needed (default 10) | |
| offset | No | ||
| category | No | Category ID, e.g. finance.crypto (see list_categories) | |
| reachable | No | true = answered at the last check | |
| transport | No | ||
| capability | No | Declared at initialize | |
| similar_to | No | Registry name of a server to find alternatives for | |
| min_success_7d | No | Daily check success over 7 days |