Skills/PyPI/shepp-lambda-mcp

shepp-lambda-mcp@2.3.2

VERIFIED· install only

Publisher claims: "A Model Context Protocol (MCP) server for AWS Lambda Tools using ChukMCPServer" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher sam-shepp · publishing for 202 daysInstalls 486Last detonated 2 h ago
$claude mcp add shepp-lambda-mcp -- uvx shepp-lambda-mcp
WatchReport an issue

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
2 of 2 bundled scripts run with no arguments, with decoy credentials in the environment · every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
AWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYAWS_SESSION_TOKENConfiguration, not credentials: AWS_PROFILE, AWS_REGION, FUNCTION_INPUT_SCHEMA_ARN_TAG_KEY, FUNCTION_LIST, FUNCTION_PREFIX, FUNCTION_TAG_KEY, FUNCTION_TAG_VALUE, LAMBDA_INVOKE_READ_TIMEOUT
Where it talks to
no vendor host named in the code
What the honeypot saw
no credential files read · no network
What we could not test
use of the skill by an agent

Connect it with a scoped credential, under the guard. It asks for AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --net declared -- uvx shepp-lambda-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-18 and scored it 88/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.1sprocessno install scripts in bundle
0.1sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.1sprocessexited 1: ./docker-healthcheck.sh: line 19: pgrep: command not found
0.1sprocessbundled script run in the sandbox with no arguments
0.2sprocessexited 1: ModuleNotFoundError: No module named 'boto3'
0.2sprocess2 of 2 bundled scripts run with no arguments
0.2sprocessscript backend runs setup only
0.2sprocessscript backend runs setup only
0.2sprocessno install scripts to re-run

Static findings

MEDIUM
Remote installer piped to shell.github/workflows/README.md:101 · Remote installer piped to shellcurl -LsSf https://astral.sh/uv/install.sh | shFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST07
MEDIUM
Pipe-to-shell pattern.github/workflows/README.md:101 · Pipe-to-shell pattern — downloads and immediately executes remote codecurl -LsSf https://astral.sh/uv/install.sh | shFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST06
MEDIUM
File permission modification commandDockerfile:71 · File permission modification command — agent changes file ownership/permissionschmod o+x /rootFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05

Cost to the agent

Instructions loaded
≈58 tok
1 file · 52 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

No advisories in OSV for shepp-lambda-mcp@2.3.2 as of 1 h ago. This is the package itself, not its dependencies.

shepp-lambda-mcp@2.3.2 safety verdict: Verified (install only) — KillerSkills