server-proxy

server-proxy is a proxy service intended to sit between a client and one or more upstream servers, forwarding requests/responses. Specific behavior (routing rules, supported transports, auth, logging, etc.) cannot be determined from the provided information.

Evaluated Apr 04, 2026 (27d ago)
Homepage ↗ Repo ↗ Infrastructure proxy reverse-proxy networking infrastructure
⚙ Agent Friendliness
19
/ 100
Can an agent use this?
🔒 Security
26
/ 100
Is it safe for agents?
⚡ Reliability
20
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
0
Documentation
10
Error Messages
0
Auth Simplicity
50
Rate Limits
0

🔒 Security

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

No concrete security documentation or configuration details were provided. As a proxy, it should ideally enforce HTTPS, validate/limit forwarded headers, and implement clear authentication/authorization; these cannot be verified from the given data.

⚡ Reliability

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

Use Cases

  • Forwarding requests from internal clients to external or upstream services
  • Centralized traffic handling (e.g., routing, header normalization) for downstream services
  • Providing a stable endpoint while upstream services change

Not For

  • Security-critical gateways without clearly documented authentication/authorization and transport protections
  • Use cases requiring guaranteed idempotency/retry semantics unless explicitly documented
  • Situations where a fully specified API contract (OpenAPI/SDK) is required

Interface

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

Authentication

OAuth: No Scopes: No

Authentication/authorization mechanisms are not described in the provided content.

Pricing

Free tier: No
Requires CC: No

No pricing information provided.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • As a proxy, request/response behaviors (timeouts, streaming, retries) may be non-obvious without explicit documentation.
  • Authentication and header-handling details may affect agent integration if not clearly specified.

Alternatives

Full Evaluation Report

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

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