mcpField
M
MCPLookup

MCPLookup

Remote
mcplookup.comSecurity0Updated 10w ago

About MCPLookup

MCPLookup is a trust-evidence service for developers and agents evaluating MCP servers. Its stdio package forwards requests to the hosted service, which returns server matches, current trust assessments, supporting evidence, and citations.

Key features

  1. 01Resolve names and packages to servers
  2. 02Find servers using normalized taxonomy
  3. 03Retrieve Trust Index and verdict
  4. 04Return evidence and citations
  5. 05stdio forwarding wrapper

Use cases

  1. 01Check a server’s trust evidence before connecting
  2. 02Find servers matching a category or name
  3. 03Connect from a client that requires local stdio

MCP support

The hosted MCP server exposes three anonymous, read-only tools for resolving, finding, and checking trust information about servers. A local stdio wrapper forwards MCP messages to the canonical remote endpoint without changing results.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcplookup.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Packages
npm@mcplookup/mcp0.1.6

Tools

3
ParameterTypeRequiredDescription
identifierstringYesExact package identifier, endpoint URL, canonical name, or complete organization, product, or service name.

Details

From the project README

MCPLookup MCP

npm tests license MCPLookup Trust Index: gold, 89 out of 100

The official stdio compatibility wrapper for the MCPLookup remote MCP server—the independent trust layer for MCP.

The canonical server is https://mcplookup.com/mcp. It provides three anonymous, read-only tools:

  • resolve_server resolves a title, package, endpoint, or name to a canonical server.
  • find_servers finds up to five servers using MCPLookup's normalized taxonomy.
  • trust_lookup returns the current Trust Index, verdict, evidence, and citation.

This package exists for MCP clients that require a local stdio command. It forwards MCP messages to the canonical hosted server without implementing scoring, storing evidence, adding authentication, or changing tool results.

Connect

Connect directly when your client supports remote Streamable HTTP:

https://mcplookup.com/mcp

Use this package when your client requires a local stdio command:

Node.js 20 or newer is required. No API key or environment variable is needed.

npx -y @mcplookup/mcp

Generic MCP client configuration:

{
  "mcpServers": {
    "mcplookup": {
      "command": "npx",
      "args": ["-y", "@mcplookup/mcp"]
    }
  }
}

Prefer a direct Streamable HTTP connection to https://mcplookup.com/mcp when your client supports remote MCP servers. The package is a transport adapter, not a separate service.

MCP Registry

MCPLookup is listed in the official MCP Registry as com.mcplookup/mcp. The name is verified through DNS control of mcplookup.com.

One entry covers both connection paths, so a client installing from the Registry can use whichever it supports:

PathDeclaration
Canonical remotestreamable-http → https://mcplookup.com/mcp
Compatibility packagenpm @mcplookup/mcp, stdio transport

The entry declares no environment variables, headers, or credentials, matching the anonymous public interface. server.json in this repository is the source of that metadata.

What stays remote

The wrapper contains no trust scores, evidence database, taxonomy, authentication system, or scoring logic. MCPLookup evaluates public evidence at the canonical service and returns the same bounded, current-state response whether a client connects directly or through this stdio adapter.

The MIT license covers the plugin and wrapper software in this repository only. It does not license MCPLookup's hosted evidence database, assessments, verdicts, scores, classifications, taxonomy, historical record, or scoring framework. Use of service data remains governed by the MCPLookup terms.

Data and security

The wrapper has no credentials and writes no local data. Requests are sent to MCPLookup's hosted endpoint, where bounded security and product telemetry are processed under the MCPLookup privacy policy. See the MCP documentation for the public interface contract.

Report security issues according to SECURITY.md. For product support, email [email protected].

Bug reports and narrowly scoped compatibility improvements are welcome. See CONTRIBUTING.md before opening a pull request.

Development

npm test
npm pack --dry-run

The package intentionally has zero runtime dependencies.

Marketplace package

This repository also contains the shared MCPLookup marketplace package:

  • .claude-plugin/plugin.json and .mcp.json package the remote server for Claude.
  • .codex-plugin/plugin.json packages the same remote server for ChatGPT and Codex.
  • skills/verify-mcp-server/SKILL.md adds the proactive pre-connect verification workflow.
  • review/marketplace-cases.md defines the positive, negative, and direct-connect release cases.

The skill improves orchestration but is not required for correct tool selection. Direct MCP, Registry, npm-wrapper, and VS Code clients receive independently useful tool descriptions and server instructions from the canonical hosted service.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.