Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MCPLookup

REMOTE · MCPLOOKUP.COM · 2 COMPONENTS · SCANNED SEP 21

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

0 this week 87 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
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
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.

remote · mcplookup.com

# add to Claude Code
claude mcp add --transport http com-mcplookup-mcp 'https://mcplookup.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-mcplookup-mcp": {
      "url": "https://mcplookup.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-mcplookup-mcp": {
      "type": "http",
      "url": "https://mcplookup.com/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add com-mcplookup-mcp --url 'https://mcplookup.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-mcplookup-mcp:
    url: "https://mcplookup.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-mcplookup-mcp": {
      "Transport": "http",
      "Url": "https://mcplookup.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-mcplookup-mcp -t streamable-http -u 'https://mcplookup.com/mcp'
// mcp.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 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.

  • 7 Sept 26 0
    • Stability: 0.97 → pass security
  • 6 Sept 26 +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.

  • 4 Sept 26 +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.

  • 2 Sept 26 +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.

  • 31 Aug 26 +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.

  • 29 Aug 26 +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.

  • 27 Aug 26 +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.

  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 21 Sept 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. present 19718 13 Verified
mcplookup.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
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
MCP tools · 3 exposed · ~435 tokens

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 →

Tool Tokens
find_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.

NameTypeReqDescription
capabilitystringNormalized capability category; required when query is omitted.
industrystringOptional normalized industry category.
kindstringOptional deployment kind.
limitintegerNumber of results; hard maximum 5.
order_bystring
querystringFree-text discovery query when no exact server is known, such as 'postgres database'.
NameTypeReqDescription
filtersobject
has_morebooleanyes
identityyes
order_bystringyes
serversarrayyes

No examples provided.

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

NameTypeReqDescription
identifierstringyesExact package identifier, endpoint URL, canonical name, or complete organization, product, or service name.
NameTypeReqDescription
has_morebooleanyes
identityyes
matchesarrayyes
statusstringyes

No examples provided.

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.

NameTypeReqDescription
server_namestringyesExact MCPLookup server name, e.g. 'io.github.owner/name'.
NameTypeReqDescription
recordyes
recoveryyes
requested_server_namestringyes
statusstringyes

No examples provided.

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.