docker-http-server

docker-http-server appears to be a Dockerized HTTP server utility intended for quickly running an HTTP endpoint (commonly used for local testing, health endpoints, or simple web services) without needing external application infrastructure.

Evaluated Apr 04, 2026 (21d ago)
Homepage ↗ Repo ↗ Infrastructure docker http server testing mocking devops
⚙ Agent Friendliness
21
/ 100
Can an agent use this?
🔒 Security
22
/ 100
Is it safe for agents?
⚡ Reliability
22
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
0
Documentation
30
Error Messages
0
Auth Simplicity
20
Rate Limits
0

🔒 Security

TLS Enforcement
10
Auth Strength
10
Scope Granularity
0
Dep. Hygiene
50
Secret Handling
50

Security posture is uncertain from the provided data. As a simple containerized HTTP server, TLS enforcement and authentication/authorization are likely not comprehensive by default. Use network isolation, run behind a reverse proxy with TLS, and add auth/rate limiting externally if this is exposed beyond localhost/testing.

⚡ Reliability

Uptime/SLA
0
Version Stability
40
Breaking Changes
30
Error Recovery
20
AF Security Reliability

Best When

You need a lightweight, quickly deployable HTTP server in a Docker-based environment for development/testing.

Avoid When

You need strong built-in security controls (authz, rate limiting, TLS termination policy) or a formally specified API contract for external consumers.

Use Cases

  • Local integration testing for HTTP clients
  • Basic healthcheck/status endpoints in dev environments
  • End-to-end testing pipelines that require a temporary HTTP server
  • Debugging webhooks/callback flows
  • Serving static/mock responses for development

Not For

  • Production-grade public internet services without additional hardening
  • Use cases requiring advanced API semantics (GraphQL/complex routing) or rich SDK support
  • Highly secure multi-tenant workloads without network isolation and authentication layers

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

No authentication mechanism could be determined from the provided information; as a Dockerized HTTP server, authentication is likely not built-in and would require external network controls or custom configuration.

Pricing

Free tier: No
Requires CC: No

No pricing information available (repository/package).

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • If the server is only a basic HTTP endpoint, there may be minimal protocol semantics (e.g., no documented error codes, retries, or idempotency).
  • Docker images can expose ports without strong defaults; agents should assume they need explicit network/TLS/auth hardening.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for docker-http-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered