Shebang Sherpa Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Nov 5, 2026

Aggregate local script portability risks without exposing script text or project names. Tools...

VerifiedSTDIODesktop onlyFiles & StorageDeveloper Tools

Overview

AI-generated overview

Local MCP server that audits a project's scripts for portability risks and returns only aggregate interpreter and permission findings.

What you can do
  • Inspect script portability across a local project without running anything
  • Report aggregate interpreter categories, executable-bit coverage and coarse portability warnings
  • Flag machine-specific or absolute interpreter paths, legacy interpreter names, executable files without shebangs, and scripts missing the executable bit
  • Return only aggregates, omitting paths, script text, project names, dependency names, arguments and environment values
When to use it
Useful when scripts work on one machine but fail on another and you want a quick, privacy-preserving check of interpreter paths and executable bits before sharing or deploying a project.
Requirements
Runs as a local stdio process installed from the npm package; Node.js is needed to build and run it. The project to scan is confined to the SHEBANG_SHERPA_ROOT environment variable. No authentication or API keys are declared.
Before you install
Read-only by design: it does not execute scripts, shells, package managers or hooks, and it skips Git metadata, dependency folders, build output and caches. It is a heuristic, not a shell parser or security scanner, so findings should be verified. Point SHEBANG_SHERPA_ROOT only at the directory you intend to audit.

Installation

In SourceWeft

  1. Open Shebang Sherpa Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

shebang-sherpa-mcp

Shebang Sherpa is a local portability audit for scripts that work on one laptop and mysteriously fail on another. It scans bounded script candidates and reports aggregate interpreter categories, executable-bit coverage, and coarse portability warnings.

Tool

  • inspect_script_portability: scan a local project without executing scripts.

The result can flag machine-specific interpreter paths, legacy interpreter names, absolute system interpreters, executable files without shebangs, and scripts missing the executable bit. It never returns paths, script text, project names, dependency names, command arguments, or environment values.

Safety

  • Reads files only. It never executes a script, shell, package manager, hook, or launcher.
  • Skips Git metadata, dependency folders, build output, coverage, and common caches.
  • Uses a bounded file count and file size.
  • Confines the project to SHEBANG_SHERPA_ROOT.
  • This is a portability heuristic, not a shell parser or security scanner.

Run

bash
npm installnpm run buildnode dist/index.js

Source: README.md at commit 0ba9d0f

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.