stun-turn-server

Stun/turn server component intended to facilitate NAT traversal for real-time networking (e.g., WebRTC) using STUN and TURN protocols.

Evaluated Apr 04, 2026 (21d ago)
Homepage ↗ Repo ↗ Infrastructure stun turn webrtc nat-traversal networking relay udp real-time
⚙ Agent Friendliness
18
/ 100
Can an agent use this?
🔒 Security
38
/ 100
Is it safe for agents?
⚡ Reliability
21
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

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

🔒 Security

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

As a network-facing STUN/TURN component, it should be hardened with least-privilege network exposure and strong TURN credentials. Exact TLS/auth configuration, secret handling, and dependency hygiene cannot be confirmed from the provided information.

⚡ Reliability

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

Best When

You need STUN/TURN functionality and can run/operate the server yourself in a controlled network environment.

Avoid When

You cannot operate and harden network-facing UDP/TCP services or do not have control over firewall/ports and certificates/configuration.

Use Cases

  • NAT traversal for VoIP/video conferencing
  • WebRTC connectivity for peers behind NAT/firewalls
  • Relay media when direct UDP connectivity fails

Not For

  • General HTTP API access
  • Credentialed business logic or data storage
  • Production signaling/identity services

Interface

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

Authentication

Methods: Static/shared credentials for TURN (commonly long-term credentials)
OAuth: No Scopes: No

Auth mechanisms are not fully verifiable from the provided information; TURN deployments typically require credentials/configuration (e.g., users/passwords), but exact method(s) cannot be confirmed here.

Pricing

Free tier: No
Requires CC: No

Self-hosted; cost is primarily infrastructure/egress and operational effort (exacts not provided).

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • No explicit programmatic interface was provided (this appears to be a network server rather than an API).
  • Operational dependencies (ports/UDP reachability, firewall rules, relay configuration) can cause failures that look like application errors.
  • TURN relay deployments can be sensitive to misconfiguration, leading to high bandwidth costs or connection failures.

Alternatives

Full Evaluation Report

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