Ministack MCP Server
ministack-mcp
PyPI
v0.1.18
Published by ministackorg — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
high Shell/command execution in server code (ministack_mcp/server.py)MTC-SRC-002
In the server's implementation (`ministack_mcp/server.py:446`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: try: result = subprocess.run( shlex.split(cmd), capture_output=True, text=
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server ministack_mcp/server.py
Tools 37
Each tool and what it can reach — statically extracted from the published source.
aws_executeno sensitive capabilitycheck_sdk_coverageno sensitive capabilitycheck_terraform_coverageno sensitive capabilitycompare_with_awsno sensitive capabilitycreate_resourceno sensitive capabilitydelete_resourceno sensitive capabilitydescribe_resourceno sensitive capabilitydiff_environmentsno sensitive capabilityexplain_errorno sensitive capabilityexport_setupno sensitive capability
Show 27 more tools ↓
find_service_for_use_caseno sensitive capabilitygenerate_test_fixtureno sensitive capabilityget_config_varno sensitive capabilityget_docker_statusno sensitive capabilityget_endpoint_infono sensitive capabilityget_migration_guideno sensitive capabilityget_quickstartno sensitive capabilityget_serviceno sensitive capabilityget_setup_statusno sensitive capabilityinvoke_lambdano sensitive capabilityis_operation_supportedno sensitive capabilitylist_config_varsno sensitive capabilitylist_resourcesno sensitive capabilitylist_servicesno sensitive capabilityministack_healthno sensitive capabilityministack_resetno sensitive capabilityministack_versionno sensitive capabilitypublish_snsno sensitive capabilityput_s3_objectno sensitive capabilityquery_dynamodbno sensitive capabilityreset_and_verifyno sensitive capabilityrun_smoke_testno sensitive capabilityscaffold_architectureno sensitive capabilitysearch_operationsno sensitive capabilitysend_sqs_messageno sensitive capabilitysuggest_next_stepsno sensitive capabilityvalidate_endpointno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (37 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 2
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.18 latest |
A 93/100 | 1 | 1.9.0 | 2026-07-24 |
v0.1.16 |
A 93/100 | 1 | 1.9.0 | 2026-07-23 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan ministack-mcp --online --registry pypiMore in Developer Tools
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Affinity Mcp Bridge MCP server.