com.lookupd/lookupd · v0.1.2 · productivity
lookupd is healthy: it completed an MCP handshake in 2355 ms and exposes 4 tools.
Find the right MCP server or skill for a task: ranked, install-ready results from 50K+ servers.
Endpoint: https://api.lookupd.com/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 4 |
| Latency | 2355 ms |
| Last checked (UTC) | 2026-11-04T02:30:31.991Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-11-04T02:30:31.991Z | Healthy | 2355 |
find_capability | 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. Lookups are free. |
get_entry | 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 |
health | 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. |
report_outcome | 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 |