node-webserver

A minimal Node.js web server utility (node-webserver) that likely starts an HTTP server and provides basic routing/handling capabilities for serving responses.

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

Score Breakdown

⚙ Agent Friendliness

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

🔒 Security

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

Insufficient information to confirm TLS enforcement, authentication/authorization, rate limiting, or secure header defaults. For production use, assume you must add HTTPS termination, authn/authz, input validation, rate limiting, and security headers via surrounding infrastructure/middleware.

⚡ Reliability

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

Best When

You need a lightweight Node HTTP server quickly (e.g., dev/prototyping) and will manage hardening separately.

Avoid When

You require strong built-in security controls (auth, rate limiting, TLS termination) or comprehensive API contracts/documentation.

Use Cases

  • Local development web server
  • Simple HTTP endpoints for prototypes
  • Educational/demo web server setup

Not For

  • Production-grade web hosting without additional hardening
  • Complex routing needs, middleware ecosystems, or large-scale deployments

Interface

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

Authentication

OAuth: No Scopes: No

Pricing

Free tier: No
Requires CC: No

Pricing not applicable for a typical open-source Node package.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • If this package is truly minimal, it may not provide structured error codes or guidance for retries/timeouts.
  • As a server, it may not define clear request/response contracts for agent-side automation unless documented in the repo examples.
  • Without explicit rate limiting/security middleware, agents should not assume safe defaults.

Alternatives

Full Evaluation Report

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

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