Container Hardening 800 190

io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.1Updated Nov 3, 2026

Reads a Dockerfile or compose file and names the hardening controls it fails, with the NIST SP 800-1

Overview

AI-generated overview

Reads a Dockerfile or compose file and reports which container hardening controls it fails, mapped to NIST SP 800-190.

What you can do
  • Analyze a Dockerfile or compose file for container hardening gaps
  • Name the hardening controls a configuration fails, referenced to NIST SP 800-190
  • No tool list is published, so the exact operations are not documented beyond this analysis.
When to use it
Useful when reviewing container build or compose configurations before deployment and you want a quick check of which hardening controls are missing.
Requirements
Runs locally as a stdio process, started with npx from the npm package @readystack/container-hardening-800-190. No authentication, environment variables or headers are declared. Desktop-only; not executable in a web client.
Before you install
The README does not describe this tool: it only mentions VS Code themes and a website, so the package's actual behavior and provenance cannot be verified from the supplied material. Treat it as unvetted and review the package before running it locally.

Installation

In SourceWeft

  1. Open Container Hardening 800 190 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

readystack-themes

Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack

Source: README.md at commit ee1c884

Tools

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

Version history

1
  1. v1.0.1LatestSep 23, 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.