Developer Tools

findanmcp.com

Searches and retrieves details about MCP servers from a registry.

1 endpoint2 known toolsFirst detected September 2, 2026Last detected September 2, 2026

ENDPOINT 1

https://findanmcp.com/mcp

No auth detected

MCP server metadata

Name: mcpfinder
Version: 0.1.3

Capabilities

tools.listChanged

Server instructions

Find an MCP server for any task: searches the official registry, Smithery and npm; remote-first. Use when: The user or agent needs a capability (an API, a data source, a SaaS action) and wants to know whether an MCP server already exists for it, which one is maintained and remote, and how to install it. Not for: Calling the found server's tools (install it instead), or building a new MCP server. Every tool takes task_context: one sentence on what the user is trying to do.

Known tools 2

find_mcp

Search for existing MCP servers that provide a capability (e.

Inferred read-only

mcp_details

Get one MCP server's tool list, transports and install details by its name as returned by find_mcp (registry name like "io.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.mcpfinder]
url = "https://findanmcp.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "mcpfinder": {
      "type": "http",
      "url": "https://findanmcp.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: mcpfinder
Remote MCP URL: https://findanmcp.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "mcpfinder": {
      "url": "https://findanmcp.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "mcpfinder": {
      "type": "http",
      "url": "https://findanmcp.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "mcpfinder",
  "transport": "streamable-http",
  "url": "https://findanmcp.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.