stork_search
Find an MCP server for a task. Say the task or product in plain words, for example: query Stripe payments, or browser automation. Results are ranked for an agent: the vendor's own server first, then servers you can connect to that answered Stork's last check. Each result is short: connect (remote URL or npm command, and whether sign-in is needed; null when Stork holds no install method), publisherDomainVerified, toolNames, and check: what Stork's own scheduled request to the endpoint last saw (result: answered | sign_in_required | stream_only | no_answer, lastCheckedAt, toolCount, toolDefinitionTokens = estimated tokens the tool definitions add to your context, toolsLastChangedAt, toolsChangedWithoutVersionChange). check is null for local stdio servers, which Stork cannot run. confidence: weak means nothing listed is a close match. A check is one initialize and one tools/list without an account: it does not prove a tool call works or that the server is safe. Listings that are duplicates of another listing, or that have not answered three checks in a row, are left out.
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": "stork_search"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | Yes | ||
| category | No | ||
| live_only | No | Only servers whose endpoint answered the last check without an account. | |
| transport | No | ||
| max_tool_tokens | No | Only servers whose tool definitions are estimated at or under this many tokens. |