$ loading_
Statically audit MCP tool surfaces for token cost, schema quality, and design issues.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "mcplint" MCP server from askskill: Run: claude mcp add --transport http 'io-github-dleibner-mcplint' 'https://mcplint-web.vercel.app/api/mcp'
Developers can statically audit MCP tool definitions before release to catch excessive token cost, weak schema quality, or poor design decisions.
When a team already has MCP tools but the cost or usability is not ideal, this tool can inspect the tool surface design and identify improvement areas.
Product managers or developers can use static audit results to evaluate design quality and cost impact when choosing between MCP interface options.
It is a tool for statically auditing MCP tool surfaces, with a focus on token cost, schema quality, and design issues.
Based on the description, it checks token cost, schema quality, and tool design issues. For the exact rule set, see the source repository.
No documentation excerpt is provided, so the installation method, runtime, and prerequisites cannot be confirmed; see the source repository.
Statically inspects MCP tool metadata for misleading instructions, hidden capabilities, and schema drift.
Audit MCP servers for spec compliance, security risks, and remediation guidance.
Run dev checks and get compact error summaries for faster debugging.
Audit MCP servers for conformance and generate scores with Markdown reports.
Statically audit Solidity contracts to find and fix common security vulnerabilities.
Audit MCP servers for conformance, tool usability, and error handling quality.