MCPLookup
REMOTE · MCPLOOKUP.COM · 2 COMPONENTS
Look up independent trust ratings and security, maintenance, and adoption evidence for MCP servers.
Available components
Last scanned (9 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 548 tokens (~182/item across 3 items; 3 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 16 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “find_servers” rewrote its description, which is the text the model reads security
- Tool “trust_lookup” rewrote its description, which is the text the model reads security
- Tool “resolve_server” rewrote its description, which is the text the model reads security
- Schema quality: 152 → 182 ▼ functional
- Tool “trust_lookup” now declares an output schema ▲ functional
- Tool “resolve_server” now declares an output schema ▲ functional
- Tool “find_servers” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- “find_servers” reworded the description of “query” cosmetic
- 14 Aug 26 0
- Tool “find_servers” rewrote its description, which is the text the model reads security
- “find_servers” added an optional parameter “query” cosmetic
- “find_servers” reworded the description of “capability” cosmetic
- “find_servers” made “capability” optional cosmetic
- 12 Aug 26 0
- Tool “resolve_server” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “resolve_server” reworded the description of “identifier” cosmetic
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://mcplookup.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcplookup.com | CN=YR1,O=Let's Encrypt,C=US | 7 Sept 2026 | 6 Dec 2026 | RSA 2048 | SHA256-RSA | 5aafaddef0b9b7b90e3fc8b85874d12db44 |
| SANs: mcplookup.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcplookup.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| mcplookup.com. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcplookup.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcplookup.com/mcp | HTTPS enforced | 308 | https://mcplookup.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_servers Find MCP servers ~195
Find a compact, trust-aware shortlist for a task or capability when no particular MCP server or product is known. Search by free text or MCPLookup's normalized capability taxonomy, with optional filters. Free text returns a reviewed identity-only slate when available; otherwise results are explicitly labelled catalog matches, and the two evidence lanes are never mixed. Returns at most five results with no pagination. A selected exact server name can be passed to resolve_server for reviewed identity context and connection options; named artifacts fit resolve_server directly.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | – | Normalized capability category; required when query is omitted. |
| industry | string | – | Optional normalized industry category. |
| kind | string | – | Optional deployment kind. |
| limit | integer | – | Number of results; hard maximum 5. |
| order_by | string | – | – |
| query | string | – | Free-text discovery query when no exact server is known, such as 'postgres database'. |
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | – |
| has_more | boolean | yes | – |
| identity | – | yes | – |
| order_by | string | yes | – |
| servers | array | yes | – |
No examples provided.
resolve_server Resolve an MCP server ~123
Resolve a named MCP server, vendor, product, package, repository, Registry identifier, or endpoint to a canonical MCPLookup identity. Returns at most five reviewed candidates with query-relative identity and publisher explanations, a compact trust assessment, and current connection options. This is the best fit when a particular artifact or product is known; find_servers covers open-ended capability discovery, while trust_lookup returns the full current evidence record for an exact canonical name.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Exact package identifier, endpoint URL, canonical name, or complete organization, product, or service name. |
| Name | Type | Req | Description |
|---|---|---|---|
| has_more | boolean | yes | – |
| identity | – | yes | – |
| matches | array | yes | – |
| status | string | yes | – |
No examples provided.
trust_lookup MCPLookup trust lookup ~117
Return MCPLookup's complete current trust record for one exact canonical MCP server name. Includes the verdict, Trust Index band and 0–100 score with confidence, coarse safety, maintenance, adoption, and provenance bands, coverage, freshness, public evidence, and citation. This fits trust questions and evidence review after identity is known; resolve_server handles ambiguous names or coordinates. Current state only—no history or safety certification.
| Name | Type | Req | Description |
|---|---|---|---|
| server_name | string | yes | Exact MCPLookup server name, e.g. 'io.github.owner/name'. |
| Name | Type | Req | Description |
|---|---|---|---|
| record | – | yes | – |
| recovery | – | yes | – |
| requested_server_name | string | yes | – |
| status | string | yes | – |
No examples provided.
How do I install the MCPLookup MCP server?
MCPLookup is a hosted endpoint at https://mcplookup.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 · mcplookup.com
claude mcp add --transport http com-mcplookup-mcp 'https://mcplookup.com/mcp'
What is the MCPLookup MCP server?
MCPLookup is an MCP server listed in the public MCP registry as com.mcplookup/mcp. Look up independent trust ratings and security, maintenance, and adoption evidence for MCP servers. This page covers its hosted endpoint (https://mcplookup.com/mcp).
Is the MCPLookup MCP server safe to use?
MCPLookup scores 87 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 MCPLookup MCP server expose?
MCPLookup exposes 3 tools: resolve_server, find_servers, trust_lookup. Their descriptions and schemas cost roughly 435 tokens of context every time the server is loaded.
Does the MCPLookup MCP server require authentication?
No. We connected to MCPLookup without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MCPLookup MCP server still maintained?
MCPLookup 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.
What did VerifyMCP test on the MCPLookup MCP server?
VerifyMCP ran 13 checks on MCPLookup, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.