Ministack Mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Ministack Mcp (Agent Skill) and scored it 45/100 (orange). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 2 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 2 flagged
A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.
*.sig, SIGNATURES) outside the documentation.Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
<!-- mcp-name: io.github.ministackorg/ministack-mcp -->
Your local AWS runtime for AI agents. A Model Context Protocol server that lets any IDE-resident AI agent (Claude Desktop, Cursor, Continue, Devin, Cline, …) act against a local MiniStack environment — deploy code, create infrastructure, run AWS CLI commands, run smoke tests, export live state as IaC — and answer deterministic, version-pinned questions about MiniStack's emulated services, supported operations, config vars, and parity status.
The knowledge side is backed by catalog.json + parity.json, generated once at build time from the MiniStack codebase, so those answers are stable, fast, and tied to the exact MiniStack version you have running. The action side talks to the live emulator at MINISTACK_ENDPOINT_URL.
You say "test my Lambda." The agent reads your code, deploys it, invokes it, and tells you if it works. You say "apply my Terraform." The agent runs it against the local environment and shows you what happened. You never think about MiniStack — you think about your code.
pipx install ministack-mcp
# or
uvx ministack-mcpSet MINISTACK_ENDPOINT_URL (default http://localhost:4566) if you run MiniStack on a non-default port.
Around 40 tools, grouped by what they do:
Knowledge (from `catalog.json` / `parity.json`) — list_services, get_service, is_operation_supported, search_operations, list_config_vars, get_config_var, get_endpoint_info, find_service_for_use_case, compare_with_aws.
State & health — ministack_version, ministack_health, ministack_reset, reset_and_verify, validate_endpoint, get_setup_status, get_docker_status.
Act on the live emulator — aws_execute (any AWS CLI command), create_resource, delete_resource, list_resources, describe_resource, invoke_lambda, put_s3_object, query_dynamodb, send_sqs_message, publish_sns.
Test & generate — run_smoke_test, check_terraform_coverage, check_sdk_coverage, generate_test_fixture, scaffold_architecture, export_setup, diff_environments, explain_error, suggest_next_steps.
*Docs (also exposed as `ministack://docs/ MCP resources)** — get_readme, get_quickstart, get_docker_doc, get_terraform_doc, get_testing_doc, get_faq_doc, get_migration_guide`.
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"ministack": {
"command": "uvx",
"args": ["ministack-mcp"],
"env": {
"MINISTACK_ENDPOINT_URL": "http://localhost:4566"
}
}
}
}~/.cursor/mcp.json:
{
"mcpServers": {
"ministack": {
"command": "uvx",
"args": ["ministack-mcp"]
}
}
}.continuerc or ~/.continue/config.json){
"experimental": {
"modelContextProtocolServers": [
{
"transport": {
"type": "stdio",
"command": "uvx",
"args": ["ministack-mcp"]
}
}
]
}
}Devin adds MCP servers from its web UI, not a local config file:
(requires the Manage MCP Servers permission).
uvx and Argsministack-mcp. Add MINISTACK_ENDPOINT_URL to the environment if you run MiniStack on a non-default port.
VS Code settings, cline.mcpServers:
{
"ministack": {
"command": "uvx",
"args": ["ministack-mcp"]
}
}Codex uses the same local MCP contract as the other agents in this repo. Keep MINISTACK_ENDPOINT_URL pointed at the MiniStack instance you want to use.
Register the server with the local uvx entry point:
{
"mcpServers": {
"ministack": {
"command": "uvx",
"args": ["ministack-mcp"]
}
}
}If you need a non-default backend:
export MINISTACK_ENDPOINT_URL=http://localhost:4566
uvx ministack-mcpUse the same MCP server definition in the Codex app settings:
{
"mcpServers": {
"ministack": {
"command": "uvx",
"args": ["ministack-mcp"]
}
}
}If the app exposes a separate MCP settings screen, add the same command and args pair there.
When MiniStack itself changes, regenerate the catalog before publishing a new release of ministack-mcp:
python build_catalog.pyThis rewrites catalog.json in place. parity.json is hand-curated and is never touched by the generator.
build_catalog.py walks ministack/services/*.py and extracts AWSoperation names from action dicts, equality compares, match/case blocks, URL-path dispatch dicts, and module docstrings.
ministack/ for os.environ.get / os.getenv /os.environ[...] to inventory every env var the emulator reads.
catalog.json, is shipped with the package.parity.json adds curated status (full / partial / stub / paid /data-plane / unsupported), real-backend flags, persistence, and gotchas.
server.py reads both files at import time and exposes the tools aboveover MCP stdio. The knowledge tools answer from the catalog; the action tools (aws_execute, invoke_lambda, create_resource, …) talk to the live emulator at MINISTACK_ENDPOINT_URL.
MIT.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.