find_mcp_servers
Search the official MCP Registry (~65,000 servers) by keyword. Matches name, title and description; ranks servers whose remote endpoint passed a live initialize check first, then by number of tools. Returns name, title, description, remote/package types, health (ok = works without auth, auth = alive but needs auth, fail = unreachable), tool count and a registry link.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"query": "<query>"
},
"name": "find_mcp_servers"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (1-25). | |
| query | Yes | Keywords, e.g. 'postgres database' or 'github issues'. | |
| category | No | Optional category filter, e.g. 'finance & crypto', 'databases' (substring match). | |
| transport | No | remote = hosted endpoint, package = installable (npm/pypi/...), any (default). | |
| working_only | No | Only servers whose remote endpoint responded OK or requires auth (default true). Package-only servers are kept unless transport is 'remote'. |