Shebang Sherpa MCP server

by mrfentmen·io.github.mrfentmen/shebang-sherpa-mcp·v1.0.0

No reviews yet

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

A85/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A85/100

full report

Adoption

New

0 stars

Reviews

Write one

Nobody has reviewed Shebang Sherpa yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Shebang Sherpa tools (1)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

inspect_script_portability
Aggregate local script interpreter and launcher portability signals without returning paths, script text, project names, dependency names, or command arguments.

Public scan report

scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it

no findings

Code scan8 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 85 days ago12/15
Maintainer identityregistry namespace matches repository owner6/10

Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Shebang Sherpa compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 85/100; higher than 70% of 48,255 servers
Tools: 1; the typical server has 7
Tools that change things: 0%; typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 1 read

Install Shebang Sherpa in Claude Code, Cursor or VS Code

Runs npx -y shebang-sherpa-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add shebang-sherpa-mcp -- npx -y shebang-sherpa-mcp

Add to Cursor

What the publisher says

From the Shebang Sherpa repository's README, as published. We do not edit it. Read it on GitHub

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

inspectscriptportability: 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 SHEBANGSHERPAROOT.
This is a portability heuristic, not a shell parser or security scanner.

Run

npm install
npm run build
node dist/index.js

Nothing above is checked by us. What we check is on the safety report.

Shebang Sherpa: common questions

Is Shebang Sherpa MCP server safe?: Yes, by our scan: it is graded A (85/100). Read the Shebang Sherpa safety report
How do I install Shebang Sherpa?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Shebang Sherpa need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Shebang Sherpa maintained?: The last commit was 87 days ago (2026-08-09). The latest release is v1.0.0.
How does Shebang Sherpa compare with other MCP servers?: safety score 85/100 (higher than 70% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.