# oh-my-mcp

> oh-my-mcp — didrod205-oh-my-mcp. Use this tool when you need to lint your MCP server to identify potential issues that could cause model failures, such as invalid tool definitions or input schemas. It checks for problems like weak descriptions, naming conflicts, and excessive context budgets, taking a tools/list JSON or live server input over stdio. Ideal for use before deploying models to ensure smooth functionality and prevent errors.

Canonical page: https://skillsregistry.net/skills/didrod205-oh-my-mcp  
JSON: https://api.skillsregistry.net/v1/skills/didrod205-oh-my-mcp

## Description

Lint your MCP server before a model chokes on it. Checks MCP tool definitions — names that break function-calling, weak descriptions, invalid input schemas, and the context budget your toolset eats every request — from a tools/list JSON or by speaking the protocol to a live server over stdio. Local, no API key.

## Trust

- **Trust score (0–1):** 0.50
- **Verification tier:** unverified

## Facts

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

## Source

- **Source listing:** [GitHub](https://github.com/didrod205/oh-my-mcp)

## 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": "didrod205-oh-my-mcp"
    }
  }
}
```

REST: `GET https://api.skillsregistry.net/v1/skills/didrod205-oh-my-mcp` · pull for local use: `GET https://api.skillsregistry.net/v1/skills/didrod205-oh-my-mcp/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