oh-my-mcp
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.
Description supplied by the publisher; it is a claim, not verified evidence.
- Name
- github:didrod205/oh-my-mcp
- Listed in
- GitHub
- Publisher
- @didrod205
- Published
- 2026-06-17
- License
- MIT
- Evidence
- Listed only, not analyzed yet
Source: https://github.com/didrod205/oh-my-mcp
What a full analysis of oh-my-mcp checks
Not checked yet. About 60 tools are analyzed every hour; each check links to its source when it runs:
- Publisher identity: not checked yet
- Repository ownership: not checked yet
- Organization verification: not checked yet
- Artifact provenance: not checked yet
- Source availability: not checked yet
- Version evidence: not checked yet
- Known vulnerabilities: not checked yet
- Install scripts: not checked yet
- Maintenance: not checked yet
- License: not checked yet
Before you install it
- Open the repository and confirm the account is the one you expect: look-alike names are common.
- Read what it asks for: files, accounts, network access and credentials it needs.
- Prefer a version from a verified publisher when one exists.