# lookupd

> Find the right MCP server or skill for a task: ranked, install-ready results from 50K+ servers.

- name: com.lookupd/lookupd
- version: 0.1.2
- connection class: R0 (autonomous)
- trust: 100/100
- quality: 73/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.lookupd%2Flookupd
- tools: https://api.protogrid.dev/v1/servers/com.lookupd%2Flookupd/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "lookupd": {
      "type": "http",
      "url": "https://api.lookupd.com/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 100
- freshness: 100
- provenance: 100
- drivers: +repository +namespace-matches-repo +dns-namespace +website +reachable +uptime-100% +updated-4d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 73/100 (new)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 71 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: get_entry (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); health (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); report_outcome (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 1,150 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool history recorded for 3 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: deps.dev does not know lookupd@0.1.2

- tools: 4, about 1,150 tokens to load them all
- tool set hash: 31f718b0bbf274f35eee0860588c7159
- tools last changed: 2026-11-04T06:08:45.040Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.lookupd/lookupd.svg)](https://protogrid.dev/servers/com.lookupd/lookupd)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-11-04 `health` changed (description) **meaning changed**
  - before: Registry status and last-seen time for an entry. Live probe data (uptime, latency, schema drift) is not yet available.
  - after: 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.
- 2026-11-04 `find_capability` changed (inputSchema)

Full history: https://api.protogrid.dev/v1/servers/com.lookupd%2Flookupd/changes

## Dependencies

- npm lookupd@0.1.2: unknown

Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0.

## Remotes

- https://api.lookupd.com/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

- npm lookupd@0.1.2

## Tools (4)

- `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 several entries launch the same url or package, `matches` lists them all, most likely first.
- `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 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.