Skip to main content
Glama
0xNagato

skill-lint

by 0xNagato
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to skill-lint

No user-submitted related servers found.

    Related Servers

    • teeshield

      teehooai
      A
      license
      A
      quality
      D
      maintenance
      Static security linter for MCP servers. Scans tool definitions for vulnerabilities (path traversal, SQL injection, SSRF), scores description quality, and auto-rewrites descriptions for safer agent tool selection.
      2
      10
      MIT

    • skillguard

      RudrenduPaul
      A
      license
      A
      quality
      A
      maintenance
      Security scanner for third-party AI agent-skill files: SKILL.md manifests, hooks, and bundled scripts, exposed via an MCP tool.
      1
      149 npm
      1
      Apache 2.0

    • tar-engine

      qingxuantang
      A
      license
      Not graded
      quality
      B
      maintenance
      Audits AI agent skills for safety using static, semantic, adversarial, and supply-chain analysis, providing scores and risk flags. Can be run via CLI, CI, or as an MCP tool from Claude Code, Cursor, and Codex.
      2
      Apache 2.0

    • MCP Tool Security Inspector

      danveil
      A
      license
      Not graded
      quality
      A
      maintenance
      Performs explainable, deterministic static analysis of MCP tool metadata to detect misleading instructions, concealed capabilities, and schema drift without executing tools.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are cleanly separated by input target: lint_skills operates on SKILL.md files/directories, while lint_mcp_tools operates on MCP tool schema JSON. There is no realistic way to confuse the two, since each description names a distinct artifact and use case.

    Naming Consistency5/5

    Both names follow an identical verb_noun pattern (lint_skills, lint_mcp_tools) with consistent snake_case and a shared 'lint_' prefix that signals the server's purpose. Fully predictable.

    Tool Count4/5

    Two tools map directly to the server's two linting domains, so each earns its place and the surface is tightly scoped. It is slightly thin—there is no config, list, or fix operation—but not unreasonably so for a focused linter.

    Completeness4/5

    The linter covers both advertised domains and reports a broad range of issues (descriptions, naming, size, duplicates, similarity, token cost). Missing auto-fix or rule-configuration operations are minor gaps an agent can work around.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources