Skip to main content
ClaudeWave
shibley avatar
shibley

mymcptools-mcp-server

Ver en GitHub

MCP server for discovering MCP servers and checking whether they are actually reachable — live handshake probes, not self-reported metadata.

MCP ServersRegistry oficial0 estrellas0 forksJavaScriptMITActualizado yesterday
Install in Claude Code / Claude Desktop
Method: Manual
Claude Code CLI
git clone https://github.com/shibley/mymcptools-mcp-server
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "mymcptools": {
      "command": "node",
      "args": ["/path/to/mymcptools-mcp-server/dist/index.js"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
💡 Clone https://github.com/shibley/mymcptools-mcp-server and follow its README for install instructions.
Casos de uso

Resumen de MCP Servers

# MyMCPTools MCP Server

An MCP server for finding other MCP servers — and, more usefully, for checking whether the one you are about to recommend is actually reachable.

Every uptime figure it returns comes from a real MCP handshake against the server's remote endpoint, not from self-reported metadata in a README.

Backed by [mymcptools.com](https://mymcptools.com). No API key required.

## Install

### Remote endpoint (recommended — nothing to install)

The server is hosted. If your client speaks Streamable HTTP, point it straight at:

```
https://mymcptools.com/api/mcp
```

Stateless, read-only, no auth, no API key. This is also the entry published to the
[official MCP Registry](https://registry.modelcontextprotocol.io) as
`io.github.shibley/mymcptools`.

### Local stdio adapter

The code in this repo is a thin stdio adapter over that same endpoint, for clients
that don't speak Streamable HTTP yet. **It is not on npm yet**, so build it from
source (Node.js 18+):

```bash
git clone https://github.com/shibley/mymcptools-mcp-server.git
cd mymcptools-mcp-server
npm install && npm run build
```

Then point your client at the built entrypoint:

```json
{
  "mcpServers": {
    "mymcptools": {
      "command": "node",
      "args": ["/absolute/path/to/mymcptools-mcp-server/dist/index.js"]
    }
  }
}
```

Add that to `claude_desktop_config.json` (Claude Desktop), `.cursor/mcp.json` (Cursor), or your client's equivalent.

Set `MYMCPTOOLS_MCP_URL` to override the upstream endpoint the adapter talks to.

## Tools

| Tool | What it answers |
|---|---|
| `search_mcp_servers` | Which servers match this keyword, category, client integration or install type? |
| `get_mcp_server` | Full entry for one server: install command, repo, supported clients, current probe verdict. |
| `get_server_status` | Is this server reachable right now? Verdict, exposed tool count, handshake latency, negotiated protocol version. |
| `get_server_history` | Trailing probe history and a daily uptime sparkline for one server. |
| `list_server_incidents` | Reconstructed outages — contiguous runs of failed probes, with start, end and duration. |
| `list_schema_drift` | Which servers added, removed or changed tools between probes. Useful for spotting breaking changes. |
| `list_categories` | Every category and client integration, with counts. Returns the valid slugs for the filters above. |
| `get_catalog_stats` | Population-level health: verdict breakdown, transport mix, latency percentiles. |

## What the probe data does and does not cover

Worth stating plainly, because the numbers are easy to misread:

- The catalog carries **~2,700 entries**, but only **~44 are probeable** — that is, they publish a remote endpoint something can actually connect to.
- The rest are **local-only servers** (stdio, run via `npx` or `docker` on your machine). There is no remote endpoint to handshake against, so they are reported as `UNPROBEABLE` rather than assigned a made-up status. For those, `get_mcp_server` falls back to a static repo-freshness signal.
- `UNPROBEABLE` therefore means "not remotely checkable", **not** "broken".

So treat the live-verification tools as high-confidence for remote/hosted servers, and treat the catalog entry itself as the useful part for local ones.

## Verdicts

| Verdict | Meaning |
|---|---|
| `GOOD` | Handshake succeeded and the server listed its tools. |
| `WARN` | Reachable, but something was off — slow handshake or a degraded response. |
| `AUTH_REQUIRED` | Endpoint is live but needs credentials before it will list tools. |
| `DOWN` | Endpoint is published but the handshake failed. |
| `UNPROBEABLE` | No remote endpoint to probe — typically a local stdio server. |

## Development

```bash
npm install
npm run build
```

Smoke-test the built server over stdio:

```bash
printf '%s\n%s\n%s\n' \
  '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"t","version":"1"}}}' \
  '{"jsonrpc":"2.0","method":"notifications/initialized"}' \
  '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}' \
  | node dist/index.js
```

## License

MIT
aimcpmcp-directorymcp-servermodelcontextprotocol

Lo que la gente pregunta sobre mymcptools-mcp-server

¿Qué es shibley/mymcptools-mcp-server?

+

shibley/mymcptools-mcp-server es mcp servers para el ecosistema de Claude AI. MCP server for discovering MCP servers and checking whether they are actually reachable — live handshake probes, not self-reported metadata. Tiene 0 estrellas en GitHub y se actualizó por última vez yesterday.

¿Cómo se instala mymcptools-mcp-server?

+

Puedes instalar mymcptools-mcp-server clonando el repositorio (https://github.com/shibley/mymcptools-mcp-server) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar shibley/mymcptools-mcp-server?

+

shibley/mymcptools-mcp-server aún no ha sido auditado por nuestro agente de seguridad. Revisa el repositorio original en GitHub antes de usarlo en producción.

¿Quién mantiene shibley/mymcptools-mcp-server?

+

shibley/mymcptools-mcp-server es mantenido por shibley. La última actividad registrada en GitHub es de yesterday, con 0 issues abiertos.

¿Hay alternativas a mymcptools-mcp-server?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega mymcptools-mcp-server en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: shibley/mymcptools-mcp-server
[![Featured on ClaudeWave](https://claudewave.com/api/badge/shibley-mymcptools-mcp-server)](https://claudewave.com/repo/shibley-mymcptools-mcp-server)
<a href="https://claudewave.com/repo/shibley-mymcptools-mcp-server"><img src="https://claudewave.com/api/badge/shibley-mymcptools-mcp-server" alt="Featured on ClaudeWave: shibley/mymcptools-mcp-server" width="320" height="64" /></a>

Más MCP Servers

Alternativas a mymcptools-mcp-server