Container Hardening 800 190 MCP server

by jmshinhwa·io.github.jmshinhwa/container-hardening-800-190·v1.0.1·1 stars

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

A89/100grade A

What users say

No reviews yet

Safety scan

A89/100

Adoption

Growing

1 stars88 downloads/wk

Reviews

Nobody has reviewed Container Hardening 800 190 yet.

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

No tool declarations could be read from the package source. They show once the server is installed.

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

no findings

Code scan6 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 2 days ago15/15
Maintainer identityregistry namespace matches repository owner6/10

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

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

Runs npx -y @readystack/container-hardening-800-190 on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add container-hardening-800-190 -- npx -y @readystack/container-hardening-800-190

From the Container Hardening 800 190 repository's README, as published. We do not edit it. Read it on GitHub

VS Code themes by ReadyStack

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

Is Container Hardening 800 190 MCP server safe?: Yes, by our scan: it is graded A (89/100). Read the Container Hardening 800 190 safety report
How do I install Container Hardening 800 190?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Container Hardening 800 190 need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Container Hardening 800 190 maintained?: The last commit was 2 days ago (2026-11-02). The latest release is v1.0.1.
How does Container Hardening 800 190 compare with other MCP servers?: safety score 89/100 (higher than 80% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers); downloads a week 88 (more than 60% of 12,191 servers with a package). Full comparison.