lookupd

Find MCP servers that provide a capability for a task. Pass a short capability phrase (e.g. "read Linear issues"), not the user's full request. Results are ranked provisionally (no outcome evidence yet) and each includes an install snippet for the given runtime. lookupd.verification is "verified" (with lookupd.publisher, the proven domain or GitHub owner) when the publisher claimed the listing. `featured` is reserved for labeled placement and empty: placement is not offered, and `results` are never reordered or filtered by payment. Lookups are free. The response carries `lookup_id`: quote it on report_outcome, with the same `session` id and `domain`, so the outcome ties to this exact search.

Full details for one entry: raw server.json, install snippets for the runtime, lookupd metadata. Pass the registry name (e.g. io.github.acme/linear-mcp), or, for a server already in your MCP config, its remote url or its npm/PyPI package; that finds the registry name to use with report_outcome. When several entries launch the same url or package, `matches` lists them all, most likely first.

Probe status of an entry: whether its remote endpoint is up, needs a login (auth_required), is down or dead, with 7-day uptime, median latency, tool count and the last probe. Stdio-only servers are not_probeable.

After a task used an MCP server, report once per server whether it worked: servers found via lookupd in this conversation and servers already installed alike. `entry` is the registry name; for an installed server, get it from get_entry with the server's url or package (skip the report if there is no entry). `success` is required. Workflow fields, all optional: `session` (a random id you make up once per conversation, 8-64 letters, digits, _ or -, never derived from the user, project or machine; repeat it on every report in the conversation), `step` (the order in which this server was first used in the conversation, from 1), `tool` (the tool you used most on it, by name), `domain` (what the conversation is about, from the fixed list), `found_via` (lookupd or installed), `lookup_id` (the lookup_id from the find_capability response that found this server, so the outcome ties to that exact search). Structured fields only (entry, success, capability_tag, latency_bucket, runtime, error_class, session, step, tool, domain, found_via, lookup_id); never task text, prompts or paths. Rankings improve from these reports.