lookupd
REMOTE · API.LOOKUPD.COM · 2 COMPONENTS
Find the right MCP server or skill for a task: ranked, install-ready results from 50K+ servers.
Available components
Last scanned (11 hours ago)
Scores higher than 43% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 53% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 4 Nov 26 60
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.lookupd.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.lookupd.com | CN=WR3,O=Google Trust Services,C=US | 1 Nov 2026 | 30 Jan 2027 | RSA 2048 | SHA256-RSA | 672be009b5375d4110b877501ea12970 |
| SANs: api.lookupd.com | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.lookupd.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| lookupd.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.lookupd.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.lookupd.com/mcp | HTTPS enforced | 302 | https://api.lookupd.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_capability Find a capability ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Short capability phrase, 1-200 characters |
| verified_only | boolean | – | Only registered publishers (none yet) |
No output schema declared.
No examples provided.
get_entry Get an entry ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
health Health of an entry ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
report_outcome Report an outcome ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| capability_tag | string | – | – |
| entry | string | yes | – |
| error_class | string | – | – |
| latency_bucket | string | – | – |
| runtime | string | – | – |
| success | boolean | yes | – |
No output schema declared.
No examples provided.
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.
remote · api.lookupd.com
claude mcp add --transport http com-lookupd-lookupd 'https://api.lookupd.com/mcp'
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.