ndt-server

ndt-server is a server implementation for Ookla-style Network Diagnostic Tool (NDT) throughput testing, used to measure client network performance (typically download/upload throughput and related metrics).

Evaluated Apr 04, 2026 (25d ago)
Homepage ↗ Repo ↗ Infrastructure networking throughput-testing ndt self-hosted diagnostics
⚙ Agent Friendliness
23
/ 100
Can an agent use this?
🔒 Security
33
/ 100
Is it safe for agents?
⚡ Reliability
32
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

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

🔒 Security

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

Without repository/manifest evidence here, TLS/auth details and dependency status cannot be confirmed. For network-testing servers, ensure you restrict access appropriately (e.g., firewall, allowlists, rate limiting) because throughput test endpoints can be abused for bandwidth consumption.

⚡ Reliability

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

Best When

You need to run NDT throughput testing infrastructure you control (self-hosted) for testing and diagnostics.

Avoid When

You want a plug-and-play SaaS API with turnkey authentication, billing, and SDKs.

Use Cases

  • Network performance measurement for end users
  • ISP/operator monitoring and benchmarking
  • Optimizing connectivity or diagnosing network issues via throughput tests

Not For

  • Business-critical data transfer or transaction workloads
  • Production environments requiring a fully managed hosted service with SLAs
  • Use as a generic HTTP API without running a server component

Interface

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

Authentication

OAuth: No Scopes: No

Auth requirements for ndt-server are not evident from the provided information. Many NDT deployments are open to test clients, but this should be verified in the repo/docs you use.

Pricing

Free tier: No
Requires CC: No

As a server implementation, cost is primarily infrastructure (compute/bandwidth) and operational overhead, not per-request SaaS pricing.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • NDT servers are typically stateful protocol endpoints (throughput test sessions) rather than simple request/response APIs.
  • Agent integration depends heavily on the specific protocol/version (e.g., ndt5 vs other NDT families) and client compatibility.

Alternatives

Full Evaluation Report

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