Skip to main content
Glama
Ev3lynx727

mcp-shellcheck

by Ev3lynx727
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-shellcheck

  • shell-mcp by supercorp-ai

    shell-mcpofficial

    supercorp-ai
    A
    license
    Not graded
    quality
    D
    maintenance
    Gives AI agents shell access by providing a run_command tool for executing shell commands and returning stdout, stderr, and exit code.
    0
    1
    ISC

Related Servers

  • sdlc-integrity-mcp

    AsobaCloud
    A
    license
    A
    quality
    A
    maintenance
    MCP server that provides audit and safety-check tools for enterprise SDLC code integrity, enabling AI agents to scan workspaces for lifecycle gaps, mock-theater tests, DRY violations, and language-specific issues in shell, JavaScript/HTML, and Python.
    4
    6 npm
    MIT

  • mcp-lint-tools

    rog0x
    A
    license
    Not graded
    quality
    D
    maintenance
    Code linting and style checking tools for AI agents, exposed as an MCP server. Supports style checks, naming conventions, complexity analysis, dead code detection, and import analysis.
    25 npm
    MIT

  • codetest-mcp

    jihyun0410
    F
    license
    Not graded
    quality
    B
    maintenance
    MCP server for static code analysis using AST parsing and linters, providing tools to detect syntax errors, type issues, typos, and incorrect variable usage across multiple languages. It supports headless linting with tools like ast_check, lint_check, and health.
    -

  • sandbox-env-mcp

    hs3434
    A
    license
    Not graded
    quality
    B
    maintenance
    MCP server providing AI agents with persistent shells, filesystem access, and multi-machine management backed by Docker containers or remote SSH hosts.
    1
    AGPL 3.0
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.5/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have completely distinct purposes: one performs script analysis, the other provides server info. No ambiguity.

Naming Consistency5/5

Both tool names follow the pattern 'shellcheck' with an optional suffix ('shellcheck', 'shellcheck_info'), maintaining consistency.

Tool Count3/5

With only 2 tools, it is below the typical 3-15 range for a well-scoped server, but it covers the essential functionality of a shellcheck service.

Completeness4/5

The core lifecycle is covered (run analysis and check capability), but a tool to list available rules or get detailed help is missing, which is a minor gap.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources