# lookupd (remote · api.lookupd.com)

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

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.lookupd.com`: 61/100 (this document), [markdown](https://verifymcp.io/servers/com-lookupd-lookupd/api.md), [page](https://verifymcp.io/servers/com-lookupd-lookupd/api)
- npm · `lookupd`: 69/100, [markdown](https://verifymcp.io/servers/com-lookupd-lookupd/lookupd.md), [page](https://verifymcp.io/servers/com-lookupd-lookupd/lookupd)

## Channel facts

- Endpoint: `https://api.lookupd.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 595 tokens (~148/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 84/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 53% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the lookupd MCP server?

lookupd is a hosted endpoint at https://api.lookupd.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-lookupd-lookupd 'https://api.lookupd.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-lookupd-lookupd": {
      "url": "https://api.lookupd.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-lookupd-lookupd]
url = "https://api.lookupd.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-lookupd-lookupd": {
      "type": "remote",
      "url": "https://api.lookupd.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-lookupd-lookupd --url 'https://api.lookupd.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-lookupd-lookupd:
    url: "https://api.lookupd.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-lookupd-lookupd": {
      "Transport": "http",
      "Url": "https://api.lookupd.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-lookupd-lookupd -t streamable-http -u 'https://api.lookupd.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 61, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-04 (score 60)

First indexed and scored.

## MCP tools (4)

### `find_capability` (~154 tokens)

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.

Input parameters:

- `capability` (string): Optional capability tag from lookupd's taxonomy to prefer
- `kind` (string): Only mcp_server in this release
- `max_results` (integer): Default 5
- `runtime` (string): Caller's runtime; selects the install snippet
- `task` (string, required): Short capability phrase, 1-200 characters
- `verified_only` (boolean): Only registered publishers (none yet)

### `get_entry` (~155 tokens)

Get 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.

Input parameters:

- `name` (string): Registry name
- `package` (string): npm or PyPI package from the MCP config, e.g. @acme/pdf-mcp
- `runtime` (string)
- `url` (string): Remote URL from the MCP config

### `health` (~64 tokens)

Health 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.

Input parameters:

- `name` (string, required)

### `report_outcome` (~158 tokens)

Report 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.

Input parameters:

- `capability_tag` (string)
- `entry` (string, required)
- `error_class` (string)
- `latency_bucket` (string)
- `runtime` (string)
- `success` (boolean, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-lookupd-lookupd/api#diagnostics

## Score history

- 2026-11-05: 61
- 2026-11-04: 60

## Common questions

### What is the lookupd MCP server?

lookupd is an MCP server listed in the public MCP registry as com.lookupd/lookupd. Find the right MCP server or skill for a task: ranked, install-ready results from 50K+ servers. This page covers its hosted endpoint (https://api.lookupd.com/mcp).

### Is the lookupd MCP server safe to use?

lookupd scores 61 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the lookupd MCP server expose?

lookupd exposes 4 tools: find_capability, get_entry, health, report_outcome. Their descriptions and schemas cost roughly 531 tokens of context every time the server is loaded.

### Does the lookupd MCP server require authentication?

No. We connected to lookupd without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the lookupd MCP server still maintained?

lookupd is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.lookupd.com/mcp
- Repository: https://github.com/lookupd/lookupd
- Website: https://lookupd.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-lookupd-lookupd/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-lookupd-lookupd/api.json
- HTML version of this page: https://verifymcp.io/servers/com-lookupd-lookupd/api