com.lookupdPublished by lookupd.comOfficial publisherv0.1.2Updated Nov 4, 2026
Find the right MCP server or skill for a task: ranked, install-ready results from 50K+ servers.
lookupd's hosted MCP server (api.lookupd.com), published by lookupd.com; no sign-in required; Streamable HTTP; 4 tools.
No AI overview yet: these facts come from the registry entry and the server itself.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.lookupd%2Flookupd/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"lookupd": {
"type": "http",
"url": "https://api.lookupd.com/mcp"
}
}
}The registry agents call to find the right MCP server, skill or agent for a task. Free to look up. Neutral: lookupd never hosts or proxies tool calls, and rank is never for sale. Rankings are provisional until real outcome evidence exists.
This repository holds everything an agent installs:
lookupd on npm: the CLI and the npx lookupd mcp stdio bridge to the lookupd APIskills/find-capability: the skill that teaches an agent the find → approve → install → report loopThe API, crawler and ranking live in a private repository. Data: Official MCP Registry (CC0), mirrored and enriched by lookupd; lookupd is not affiliated with the MCP project.
Claude Code (plugin: skill + MCP tools):
Any agent that reads skills (skills.sh):
MCP only, any client that launches stdio servers:
.vscode/mcp.json:
.cursor/mcp.json / Claude Desktop:
Remote endpoint, for clients that connect to streamable HTTP directly: https://api.lookupd.com/mcp.
Environment: LOOKUPD_API_URL (default https://api.lookupd.com), XDG_CONFIG_HOME.
Config lives at ~/.config/lookupd/config.json.
Off by default. When you run lookupd telemetry on, the agent can call report_outcome after
using a server it found through lookupd. A report contains only: the entry name, success,
a latency bucket, your runtime, a capability tag from a fixed list, and an error class.
Never prompts, task text, file paths or output. Lookups themselves are free and unauthenticated;
the search phrase is stored truncated to 160 characters as anonymous demand data.
Policy: https://lookupd.com/telemetry
Local end-to-end against a dev API: LOOKUPD_API_URL=http://localhost:3000 npx lookupd find "linear",
and in Claude Code /plugin marketplace add /path/to/this/repo.
MIT. See LICENSE.
Source: README.md at commit ec8973d
Find a 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.
kindtaskrequiredruntimecapabilitymax_resultsverified_onlyGet an 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 several entries launch the same url or package, `matches` lists them all, most likely first.
urlnamepackageruntimeHealth of an entry
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.
namerequiredReport an 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 entry). `success` is required. Structured fields only (entry, capability_tag, success, latency_bucket, runtime, error_class); never task text, prompts or paths. Rankings improve from these reports.
entryrequiredruntimesuccessrequirederror_classcapability_taglatency_bucket100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
/plugin marketplace add lookupd/lookupd/plugin install lookupd@lookupdnpx skills add lookupd/lookupdclaude mcp add lookupd -- npx -y lookupd@latest mcp{ "servers": { "lookupd": { "command": "npx", "args": ["-y", "lookupd@latest", "mcp"] } } }{ "mcpServers": { "lookupd": { "command": "npx", "args": ["-y", "lookupd@latest", "mcp"] } } }npx lookupd find "read Linear issues" --runtime claude-codenpx lookupd find "pdf extraction" --jsonnpx lookupd telemetry on|off|statusnpx lookupd login --key lk_... # optional API keynpx lookupd mcp # stdio bridge (what the plugin runs)pnpm installpnpm test # vitest: bridge, CLI, API client, config, manifestspnpm build # tsup → dist/cli.jsclaude plugin validate .