socks5-server

socks5-server is a SOCKS5 proxy server implementation that accepts client connections and relays traffic to requested destinations using the SOCKS5 protocol.

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

Score Breakdown

⚙ Agent Friendliness

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

🔒 Security

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

As a proxy relay, it can be abused for unauthorized egress if left open. Security largely depends on deployment: network-level access restriction, optional SOCKS5 authentication, logging/monitoring, and TLS/integrity of any client connections (TLS is not implied by SOCKS5 itself—often SOCKS5 is TCP plaintext unless wrapped/proxied elsewhere). Dependency hygiene and exact auth mechanisms are not verifiable from the provided prompt content.

⚡ Reliability

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

Best When

You control the network environment (firewalling, allowlists) and need a SOCKS5 relay for compatibility/testing.

Avoid When

You need an API/SDK-first service, or you cannot restrict who can connect to the proxy.

Use Cases

  • Run a local or network-facing SOCKS5 proxy for routing client traffic
  • Provide a simple proxy layer for tools that support SOCKS5
  • Testing/debugging of proxy/network behavior using the SOCKS5 protocol

Not For

  • Production use without careful security hardening and access controls
  • Use as a general-purpose internet gateway for untrusted networks
  • Use cases requiring strong, standardized API integrations (it is a network proxy, not an application API)

Interface

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

Authentication

Methods: SOCKS5 username/password (if supported by configuration) IP allowlisting / firewalling (deployment-level)
OAuth: No Scopes: No

This is a network service rather than an API product. Authentication, if any, is typically SOCKS5-level (username/password) and/or enforced via network controls; exact support is not provided in the prompt content.

Pricing

Free tier: No
Requires CC: No

Not applicable; open-source/network software pattern (pricing unknown from provided info).

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • This is not an HTTP/SDK-based interface; agents must work at the network/protocol level (establish TCP connection, speak SOCKS5).
  • Security and access control (firewalls/allowlists, auth configuration) are critical and are typically not guaranteed by the agent framework.
  • If SOCKS5 auth is used, agents must manage credentials securely and handle protocol-level failures/rejections.

Alternatives

Full Evaluation Report

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