# inventer-dev/mcp-internet-speed-test [Health: Active]

**Category:** 📊 Monitoring  
**Repository:** https://github.com/inventer-dev/mcp-internet-speed-test  
**GitHub Stars:** 14  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/inventer-dev-mcp-internet-speed-test

## Description
Internet speed testing with network performance metrics including download/upload speed, latency, jitter analysis, and CDN server detection with geographic mapping

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "mcp-internet-speed-test": {
    "command": "uvx",
    "args": ["mcp-internet-speed-test"]
  }
}
```

## Documentation

## What inventer-dev/mcp-internet-speed-test MCP server does

The inventer-dev/mcp-internet-speed-test MCP server exposes network diagnostics through the Model Context Protocol. It can measure download and upload bandwidth in Mbps, test latency in milliseconds, calculate jitter from repeated latency measurements, inspect CDN server information, or run a combined test that returns the full set of metrics.

Results can include information about the endpoint serving the test. The server identifies supported CDN providers such as Fastly, Cloudflare, and Amazon CloudFront, and can map POP codes to physical locations. It also reports cache-related details and HTTP headers including `x-served-by`, `via`, and `x-cache` when those headers are available.

## How it works

Download testing starts with a small file and increases the file size progressively. The available test files range from 128 KB to 128 MB and are hosted in the `inventer-dev/speed-test-files` GitHub repository through Git LFS. The implementation uses a time-based threshold, with an 8-second default sustain time, to select the final measurement.

Upload tests stream data to a Cloudflare Workers endpoint hosted on `httpi.dev`, with HTTPBin listed as a fallback. Latency uses multiple samples and reports the minimum result. Jitter is calculated from latency variation, using five samples by default. A complete test combines these measurements with server and CDN metadata.

The `get_server_info` tool can inspect a URL without running a bandwidth test. CDN detection depends on response headers and routing, so the reported location reflects the server reached by the test rather than necessarily the user's physical location.

## Setup and configuration

Install the package from PyPI with Python 3.12 or later. The documented standalone commands are `pip install mcp-internet-speed-test` followed by `mcp-internet-speed-test`, or `uvx mcp-internet-speed-test` for a direct run without a separate installation. The package uses the MCP CLI framework and the `httpx` asynchronous HTTP client as dependencies.

For Claude Desktop, add a server entry whose command is `mcp-internet-speed-test`. An alternative configuration uses `uvx` with `mcp-internet-speed-test` as its argument. The README also documents Docker and development-mode installation for local contributors.

Test behavior includes configurable maximum file size, latency sample count, jitter sample count, and sustain time. The documented sustain-time range is 1 to 8 seconds, with 8 seconds as the default.

## Tools and capabilities

The available tools are:

- `measure_download_speed`: measures download bandwidth and includes server location information.
- `measure_upload_speed`: measures upload bandwidth and includes server location information.
- `measure_latency`: samples network latency and returns the minimum value.
- `measure_jitter`: analyzes latency variation and provides server information.
- `get_server_info`: retrieves CDN and response-header details for a URL.
- `run_complete_test`: runs the full measurement workflow and returns combined metrics and metadata.

## Limitations and notes

The inventer-dev/mcp-internet-speed-test MCP server requires access to its download repository and external test endpoints. Corporate firewalls, proxies, unavailable GitHub content, or blocked upload services can affect results. The upload workflow has an automatic fallback, but the README does not describe a user-configured endpoint setting.

Large files may time out on slow connections, particularly above 50 MB. CDN POP identification depends on provider headers and network routing, and therefore may be incomplete or differ between runs. The server does not require an API key in the documented setup, but it does require a suitable Python runtime or the provided container workflow.

_Full upstream README: https://allmcps.com/mcp/inventer-dev-mcp-internet-speed-test/readme_