simple-http-server

A minimal HTTP server utility/package for serving a simple server (typically to run local development endpoints and/or respond to requests). Without the specific README/manifest content, this is evaluated as a generic “simple-http-server” offering.

Evaluated Apr 04, 2026 (25d ago)
Homepage ↗ Repo ↗ Infrastructure http server web development local-testing minimal
⚙ Agent Friendliness
32
/ 100
Can an agent use this?
🔒 Security
20
/ 100
Is it safe for agents?
⚡ Reliability
20
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

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

🔒 Security

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

Likely runs without built-in auth and may not enforce TLS by itself (depends on implementation and deployment). Use external TLS termination/reverse proxy, add authentication/authorization middleware if supported, and ensure dependencies are audited.

⚡ Reliability

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

Best When

You need a lightweight HTTP server quickly and can control the environment (networking, TLS termination, auth, logging) externally.

Avoid When

You need built-in security, strict operational guarantees, or a well-defined, documented HTTP contract for external consumption.

Use Cases

  • Local development and testing of HTTP endpoints
  • Quick internal tools/prototypes that need an HTTP listener
  • Educational examples for basic HTTP serving
  • Health checks or lightweight static/dummy endpoints

Not For

  • Production-grade public web services without additional hardening (auth, TLS termination, rate limiting, observability)
  • High-security environments requiring strong access control by default
  • Latency/throughput-critical workloads without performance tuning

Interface

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

Authentication

OAuth: No Scopes: No

No authentication information provided; likely none or must be implemented by the user at the app layer.

Pricing

Free tier: No
Requires CC: No

No pricing information available (assumed open-source/local package).

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • If no documented HTTP contract is provided, agents may guess routes/behavior.
  • Minimal servers often lack structured error responses; agents may need to handle generic 4xx/5xx.
  • No rate limiting guidance may exist; agents should self-throttle when iterating.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for simple-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