# TestedMCP server

> Look up test scores, deprecation status and replacements for MCP servers that have been installed and handshake-tested.

- Listing: https://mcp.tc/i/testedmcp
- Connect: use the server's own URL `https://testedmcp.com/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Developer Tools](https://mcp.tc/c/developer-tools)
- Vendor: TestedMCP
- Homepage: <https://testedmcp.com/>

## About

TestedMCP gives read-only access to a dataset of MCP servers that were installed and handshake-tested. You can search tested servers by name, package or category, get a 0-100 score with per-test results and test date, check whether a server is deprecated, and find a maintained replacement when there is evidence for one.

Scores come from automated tests and are not quality or security ratings. The hosted streamable HTTP endpoint is public. No sign-in or API key is needed.

## What it can do

- Search tested MCP servers by name, package or category
- Get a 0-100 score with per-test results and evidence
- Check deprecation status and npm's deprecation message
- Find a maintained replacement for a deprecated server

## Tools (4)

- `search_servers`: Search tested MCP servers by name, package or category, sorted by score. (read-only)
- `get_score`: Get the 0-100 score, per-test results, evidence and test date for one server. (read-only)
- `is_deprecated`: Get deprecation status, npm's exact deprecation message and verification date. (read-only)
- `get_replacement`: Get a maintained replacement for a deprecated server when evidence exists. (read-only)

## Example prompts

- "Search TestedMCP for database MCP servers sorted by score"
- "What is the TestedMCP score for the redis-mcp-server package?"
- "Is this MCP server package deprecated?"
- "Is there a maintained replacement for this deprecated MCP server?"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

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

2. Start Claude Code and type `/mcp`. **testedmcp** should show as connected.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **TestedMCP** and paste this URL:

```url
https://testedmcp.com/mcp
```

3. Click **Add**. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=TestedMCP&connectorUrl=https%3A%2F%2Ftestedmcp.com%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://testedmcp.com/mcp` and click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://testedmcp.com/mcp` as the server URL, then for authentication choose **No authentication**.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=testedmcp&config=eyJ1cmwiOiJodHRwczovL3Rlc3RlZG1jcC5jb20vbWNwIn0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

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

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=testedmcp&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Ftestedmcp.com%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"testedmcp","type":"http","url":"https://testedmcp.com/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

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

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "testedmcp": {
      "serverUrl": "https://testedmcp.com/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add testedmcp --url https://testedmcp.com/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

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

### Gemini CLI

```bash
gemini mcp add --transport http testedmcp https://testedmcp.com/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "testedmcp": {
      "type": "http",
      "url": "https://testedmcp.com/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://testedmcp.com/mcp`.

## Recent changes

- 2026-11-12 05:53 UTC: Server instructions changed. Source: automatic check. Worth a look: new server instructions.
- 2026-11-11 17:52 UTC: Server instructions changed. Source: automatic check. Worth a look: new server instructions.
- 2026-11-05 05:30 UTC: Tracking started: 4 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/testedmcp#history (Atom feed: https://mcp.tc/i/testedmcp/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 0.1.0
- MCP protocol version: 2025-11-25
- Last checked: 2026-11-18 (reachable)
- Listed: 2026-11-05
- Updated: 2026-11-05

---
Source: https://mcp.tc/i/testedmcp (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
