# mcp-wtf

> mcp-wtf — beeeeen-mcp-wtf. Use this tool when you need to quickly diagnose and resolve connection issues with your MCP server, as it analyzes configurations and identifies problems such as missing commands, invalid API keys, and stdout pollution, providing exact fixes. It supports diagnosis of multiple servers in Claude, Cursor, and VS Code configurations. Ideal for use when experiencing connectivity problems or silent crashes with your MCP server.

Canonical page: https://skillsregistry.net/skills/beeeeen-mcp-wtf  
JSON: https://api.skillsregistry.net/v1/skills/beeeeen-mcp-wtf

## Description

Your MCP server won't connect. Find out why in 10 seconds. Diagnoses every server in your Claude/Cursor/VS Code configs - missing commands, placeholder API keys, stdout pollution, silent crashes - with the exact fix.

## Trust

- **Trust score (0–1):** 0.87
- **Verification tier:** verified
- **Last scanned:** 2026-09-28

## Facts

- **Version:** 1.0.0
- **Skill type:** atomic
- **Execution layer:** container
- **Runtime environment:** vm
- **License:** MIT
- **Updated:** 2026-09-28

## Source

- **Source listing:** [GitHub](https://github.com/Beeeeen/mcp-wtf)

## Use it

Resolve this record through the SkillsRegistry MCP server (no auth, read-only):

```
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp
```

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_skill",
    "arguments": {
      "slug": "beeeeen-mcp-wtf"
    }
  }
}
```

REST: `GET https://api.skillsregistry.net/v1/skills/beeeeen-mcp-wtf` · pull for local use: `GET https://api.skillsregistry.net/v1/skills/beeeeen-mcp-wtf/pull`

---
SkillsRegistry indexes agent skills from public registries and GitHub. Skills we have analysed are scanned with Circle-IR and scored on six dimensions; each listing states its scan coverage. More: https://skillsregistry.net/llms.txt