# MCP Finder (remote · findanmcp.com)

Find an MCP server for any task: searches the official registry, Smithery and npm; remote-first.

- Trust score: 31/100 (low)
- Change this week: −47
- Registry status: active
- Liveness: degraded
- Owner verified: no
- Last scored: 2026-09-25

> **Degraded**: one or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.

## Components

- remote · `findanmcp.com`: 31/100 (this document), [markdown](https://verifymcp.io/servers/ux-xd-mcpfinder/findanmcp.md), [page](https://verifymcp.io/servers/ux-xd-mcpfinder/findanmcp)

## Channel facts

- Endpoint: `https://findanmcp.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.3`

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

- **Endpoint Security**: 0/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the MCP Finder server?

MCP Finder is a hosted endpoint at https://findanmcp.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 ux-xd-mcpfinder 'https://findanmcp.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ux-xd-mcpfinder": {
      "url": "https://findanmcp.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ux-xd-mcpfinder": {
      "type": "http",
      "url": "https://findanmcp.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ux-xd-mcpfinder]
url = "https://findanmcp.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add ux-xd-mcpfinder --url 'https://findanmcp.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ux-xd-mcpfinder:
    url: "https://findanmcp.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ux-xd-mcpfinder": {
      "Transport": "http",
      "Url": "https://findanmcp.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ux-xd-mcpfinder -t streamable-http -u 'https://findanmcp.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ux-xd-mcpfinder": {
      "type": "http",
      "url": "https://findanmcp.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-25 (score 31, −16)

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

### 2026-09-24 (score 47, −15)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-19 (score 62, −16)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-17 (score 78, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Stability: 0.50 → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-16 (score 78, +1)

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

### 2026-09-14 (score 77, +1)

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

### 2026-09-12 (score 76, +1)

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

### 2026-09-09 (score 75, +1)

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

## MCP tools (2)

### `find_mcp` (~202 tokens)

Search for existing MCP servers that provide a capability (e.g. "postgres", "wayback machine", "google sheets"). Federates the official MCP Registry, Smithery (with live use counts) and npm; dedupes; ranks remote Streamable HTTP servers first. Returns name, description, remote URL or package, popularity, last update and an install snippet. Use before building or asking the user to build a tool.

Input parameters:

- `limit` (integer): Max results after ranking. Default 8.
- `query` (string, required): What capability you need, as 1-5 keywords (an API name, a product, a data source). Not a sentence.
- `remote_only` (boolean): Only servers reachable over HTTP without installing anything locally.
- `task_context` (string, required): One sentence on what the user is ultimately trying to do (the task this call serves). Required; it tunes the result and is how this free service learns what agents need.

### `mcp_details` (~123 tokens)

Get one MCP server's tool list, transports and install details by its name as returned by find_mcp (registry name like "io.github.owner/server", "smithery:owner/server", or "npm:package"). Use to check a server exposes the tool you need before installing it.

Input parameters:

- `name` (string, required): Exact name from find_mcp results.
- `task_context` (string, required): One sentence on what the user is ultimately trying to do (the task this call serves). Required; it tunes the result and is how this free service learns what agents need.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ux-xd-mcpfinder/findanmcp#diagnostics

## Score history

- 2026-09-25: 31
- 2026-09-24: 47
- 2026-09-23: 62
- 2026-09-22: 62
- 2026-09-21: 62
- 2026-09-20: 62
- 2026-09-19: 62
- 2026-09-18: 78
- 2026-09-17: 78
- 2026-09-16: 78
- 2026-09-15: 77
- 2026-09-14: 77
- 2026-09-13: 76
- 2026-09-12: 76
- 2026-09-11: 75
- 2026-09-10: 75
- 2026-09-09: 75
- 2026-09-08: 74
- 2026-09-07: 74
- 2026-09-06: 73
- 2026-09-05: 73
- 2026-09-04: 72
- 2026-09-03: 72
- 2026-09-02: 64
- 2026-09-01: 64

## Common questions

### What is the MCP Finder server?

MCP Finder is listed in the public MCP registry as io.github.ux-xd/mcpfinder. Find an MCP server for any task: searches the official registry, Smithery and npm; remote-first. This page covers its hosted endpoint (https://findanmcp.com/mcp).

### Is the MCP Finder server safe to use?

MCP Finder scores 31 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 MCP Finder server expose?

MCP Finder exposes 2 tools: find_mcp, mcp_details. Their descriptions and schemas cost roughly 325 tokens of context every time the server is loaded.

### Does the MCP Finder server require authentication?

Its publisher declares no required credentials for MCP Finder. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the MCP Finder server still maintained?

MCP Finder is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 16 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://findanmcp.com/mcp
- Repository: https://github.com/ux-xd/mcpfinder-mcp
- Website: https://findanmcp.com/
- Changelog RSS feed: https://verifymcp.io/servers/ux-xd-mcpfinder/findanmcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ux-xd-mcpfinder/findanmcp.json
- HTML version of this page: https://verifymcp.io/servers/ux-xd-mcpfinder/findanmcp