73trust / 100
Dockerfile Security Audit
by dockerfile-audit-mcp.mcpize.run in Security & trust
MCP serverFailing, checked 3 days ago
Audit Dockerfiles for root users, baked-in secrets, curl-pipe-shell and unpinned base images.
https://dockerfile-audit-mcp.mcpize.run/mcp- Tools
- -
- behind sign-in or payment
- Uptime
- 78.3%
- last 30 days
- Response time
- 611 ms
- 879 ms slowest 5%
- Last check
- Failed
- 3 days ago, next in 6 h
Reliability
All checks passedSome failedAll failedNot checked
Latest check failed 3 days ago: initialize returned HTTP 500
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers. It asks for sign-in, an API key or payment.
{
"mcpServers": {
"dockerfile-security-audit": {
"type": "http",
"url": "https://dockerfile-audit-mcp.mcpize.run/mcp"
}
}
}The tool list is behind sign-in or payment, so we can't show it.
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 3 days ago | initialize returned HTTP 500 | 500 | 316 ms |
| 4 days ago | initialize returned HTTP 500 | 500 | 464 ms |
| 5 days ago | initialize returned HTTP 500 | 500 | 578 ms |
| 7 days ago | initialize returned HTTP 500 | 500 | 699 ms |
| 8 days ago | initialize returned HTTP 500 | 500 | 779 ms |
Show 10 older checks
| 9 days ago | initialize returned HTTP 500 | 500 | 558 ms |
| 11 days ago | initialize returned HTTP 500 | 500 | 615 ms |
| 12 days ago | initialize returned HTTP 500 | 500 | 621 ms |
| 13 days ago | initialize returned HTTP 500 | 500 | 646 ms |
| 13 days ago | initialize returned HTTP 500 | 500 | 518 ms |
| 14 days ago | Passed | 401 | 649 ms |
| 14 days ago | Passed | 401 | 587 ms |
| 15 days ago | Passed | 401 | 606 ms |
| 15 days ago | Passed | 401 | 611 ms |
| 16 days ago | Passed | 401 | 543 ms |