# MCPLookup (remote · mcplookup.com)

Look up independent trust ratings and security, maintenance, and adoption evidence for MCP servers.

- Trust score: 87/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `mcplookup.com`: 87/100 (this document), [markdown](https://verifymcp.io/servers/com-mcplookup-mcp/mcplookup.md), [page](https://verifymcp.io/servers/com-mcplookup-mcp/mcplookup)
- npm · `@mcplookup/mcp`: 50/100, [markdown](https://verifymcp.io/servers/com-mcplookup-mcp/mcplookup-mcp.md), [page](https://verifymcp.io/servers/com-mcplookup-mcp/mcplookup-mcp)

## Channel facts

- Endpoint: `https://mcplookup.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.6`

## 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-09-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 74/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 88% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-mcplookup-mcp": {
      "type": "http",
      "url": "https://mcplookup.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-09-07 (score 87, 0)

- [security] Stability: 0.97 → pass

### 2026-09-06 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-02 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-31 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-29 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-27 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-26 (score 81, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (3)

### `resolve_server` (~123 tokens)

Resolve an MCP server

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.

Input parameters:

- `identifier` (string, required): Exact package identifier, endpoint URL, canonical name, or complete organization, product, or service name.

Output parameters:

- `has_more` (boolean)
- `identity`
- `matches` (array)
- `status` (string)

### `find_servers` (~195 tokens)

Find MCP servers

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.

Input parameters:

- `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'.

Output parameters:

- `filters` (object)
- `has_more` (boolean)
- `identity`
- `order_by` (string)
- `servers` (array)

### `trust_lookup` (~117 tokens)

MCPLookup trust lookup

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.

Input parameters:

- `server_name` (string, required): Exact MCPLookup server name, e.g. 'io.github.owner/name'.

Output parameters:

- `record`
- `recovery`
- `requested_server_name` (string)
- `status` (string)

## Diagnostics

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

## Score history

- 2026-09-21: 87
- 2026-09-20: 87
- 2026-09-19: 87
- 2026-09-18: 87
- 2026-09-17: 87
- 2026-09-16: 87
- 2026-09-15: 87
- 2026-09-14: 87
- 2026-09-13: 87
- 2026-09-12: 87
- 2026-09-11: 87
- 2026-09-10: 87
- 2026-09-09: 87
- 2026-09-08: 87
- 2026-09-07: 87
- 2026-09-06: 87
- 2026-09-05: 86
- 2026-09-04: 86
- 2026-09-03: 85
- 2026-09-02: 85
- 2026-09-01: 84
- 2026-08-31: 84
- 2026-08-30: 83
- 2026-08-29: 83
- 2026-08-28: 82
- 2026-08-27: 82
- 2026-08-26: 81
- 2026-08-25: 80
- 2026-08-24: 79
- 2026-08-23: 79

## Common questions

### 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 21 September 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://mcplookup.com/mcp
- Repository: https://github.com/mcplookupdev/mcplookup-mcp
- Website: https://mcplookup.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-mcplookup-mcp/mcplookup.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mcplookup-mcp/mcplookup.json
- HTML version of this page: https://verifymcp.io/servers/com-mcplookup-mcp/mcplookup