mcp-internet-speed-test
MCP Internet-Geschwindigkeitstest
⚠️ Experimentelle Version
Dies ist eine experimentelle Implementierung eines Model Context Protocol (MCP)-Servers für Internetgeschwindigkeitstests. Sie ermöglicht KI-Modellen und Agenten, Netzwerkleistungsmetriken über eine standardisierte Schnittstelle zu messen, zu analysieren und zu melden.
Related MCP server: Test MCP Feb4 MCP Server
Was ist MCP?
Das Model Context Protocol (MCP) bietet Large Language Models (LLMs) eine standardisierte Möglichkeit, mit externen Tools und Datenquellen zu interagieren. Stellen Sie es sich als „USB-C für KI-Anwendungen“ vor – eine gemeinsame Schnittstelle, die KI-Systemen den Zugriff auf reale Funktionen und Informationen ermöglicht.
Merkmale
Download-Geschwindigkeitstest : Download-Bandbreite messen
Upload-Geschwindigkeitstest : Messen Sie die Upload-Bandbreite mit konfigurierbaren Dateigrößen
Latenztests : Messen Sie die Netzwerklatenz zu verschiedenen Servern
Jitter-Analyse : Berechnen Sie Netzwerk-Jitter durch die Analyse von Latenzschwankungen
Umfassende Berichterstattung : Bereitstellung detaillierter Berichte im JSON-Format
Installation
Voraussetzungen
Python 3.12 oder höher
UV -Paketmanager (empfohlen)
Option 1: Verwendung von uvx (empfohlen)
Der Befehl uvx ist eine bequeme Möglichkeit, Python-Pakete direkt auszuführen, ohne sie explizit zu installieren:
# Run the MCP server directly
uvx /path/to/mcp-internet-speed-testOption 2: Verwenden von Docker
# Build the Docker image
docker build -t mcp-internet-speed-test .
# Run the MCP server in a Docker container
docker run -it --rm -v $(pwd):/app -w /app mcp-internet-speed-testKonfiguration
Um diesen MCP-Server mit Claude Desktop oder anderen MCP-Clients zu verwenden, fügen Sie ihn Ihrer MCP-Konfigurationsdatei hinzu.
Claude Desktop-Konfiguration
Bearbeiten Sie Ihre Claude Desktop MCP-Konfigurationsdatei:
{
"mcpServers": {
"mcp-internet-speed-test": {
"command": "uv",
"args": [
"--directory",
"/ABSOLUTE/PATH/TO/mcp-internet-speed-test",
"run",
"main.py"
]
}
}
}API-Tools
Der MCP Internet Speed Test bietet die folgenden Tools:
measure_download_speed: Misst die Download-Bandbreite (in Mbit/s)measure_upload_speed: Misst die Upload-Bandbreite (in Mbit/s)measure_latency: Misst die Netzwerklatenz (in ms)measure_jitter: Misst Netzwerk-Jitter durch Analyse von Latenzschwankungenrun_complete_test: Führt alle Tests aus und erstellt einen umfassenden Bericht
Fehlerbehebung
Wenn Sie Probleme beim Herstellen einer Verbindung zum MCP-Server haben:
Stellen Sie sicher, dass der Pfad in Ihrer MCP-Konfiguration korrekt ist
Überprüfen Sie, ob Sie über die erforderlichen Berechtigungen für das Verzeichnis verfügen
Überprüfen Sie, ob Python 3.12+ installiert ist und sich in Ihrem PATH befindet
Stellen Sie sicher, dass die Pakete
mcp[cli]undhttpxinstalliert sind
Entwicklung
Dies ist ein experimentelles Projekt. Beiträge sind willkommen. So können Sie mitmachen:
Öffnen Sie ein Problem oder senden Sie eine Pull-Anfrage
Lizenz
Dieses Projekt ist unter der MIT-Lizenz lizenziert – Einzelheiten finden Sie in der Datei LICENSE.
Danksagung
MCP-Framework-Betreuer zur Standardisierung von KI-Tool-Interaktionen
Die Model Context Protocol-Community für Dokumentation und Beispiele
Available Tools
6 toolsget_server_infoA
Get server information for any URL without performing speed tests.
Args:
url_download: URL to download data from
url_upload: URL to upload data to
url_latency: URL to measure latency to
Returns:
Dictionary with servers information including POP location, CDN info, etc.
Inputs: url_download, url_upload, url_latency.
measure_download_speedB
Measure download speed using incremental file sizes.
Args:
size_limit: Maximum file size to test (default: 128MB)
sustain_time: Duration in seconds for each test (1-8, default: 8)
Returns:
Dictionary with download speed results
Inputs: size_limit, sustain_time.
measure_jitterD
Jitter is the variation in latency, so we need multiple measurements.
Inputs: url, samples.
measure_latencyB
Measure the latency using multiple samples and report the minimum.
Takes a number of samples and reports the lowest
value for the most accurate representation of network latency.
Args:
url (str): The URL to measure latency to
samples (int): Number of samples to take (default: 10)
Returns:
Dictionary with latency result (minimum of all samples)
Inputs: url, samples.
measure_upload_speedB
Measure upload speed using incremental file sizes.
Args:
url_upload: URL to upload data to
size_limit: Maximum file size to test (default: 128MB)
sustain_time: Duration in seconds for each test (1-8, default: 8)
Returns:
Dictionary with upload speed results
Inputs: url_upload, size_limit, sustain_time.
run_complete_testA
Run a complete speed test returning all metrics in a single call.
This test uses the smart incremental approach inspired by SpeedOf.Me:
- First measures download speed with gradually increasing file sizes
- Then measures upload speed with gradually increasing data sizes
- Measures latency and jitter
- Returns comprehensive results with real-time data
Args:
max_size: Maximum file size to test (default: 128MB)
url_upload: URL for upload testing
url_latency: URL for latency testing
sustain_time: Duration in seconds for each test (1-8, default: 8)
Returns:
Complete test results including download, upload, latency and jitter metrics
Inputs: max_size, url_upload, url_latency, sustain_time.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: server info, download speed, jitter, latency, upload speed, and a combined test. No overlap or ambiguity.
All tool names follow a consistent verb_noun snake_case pattern (get_, measure_, run_). Even though 'measure' appears multiple times, the nouns are distinct.
6 tools is ideal for an internet speed test server, covering all key metrics plus a combined test and server info without bloat.
The set covers all standard speed test metrics: download, upload, latency, jitter, and server info. A combined test is also provided. No obvious gaps.
Maintenance
Related MCP Connectors
MCP server for building and testing AI agents with multi-model experimentation and insights.
The Remote MCP server acts as a standardized bridge between LLM applications (like Claude, ChatGPT, and Cursor) and external services, enabling AI agents to access external tools and resources. Its primary capability is providing a centralized search tool to discover other MCP servers and their respective tools. Unlike local implementations, it runs remotely with OAuth authentication and permission controls for security.
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
The OpenMesh MCP Server provides decentralized, permissionless cloud infrastructure that integrates AI assistants with Web2 and Web3 applications without middlemen. It offers intelligent service discovery to identify MCP servers, acts as a universal proxy for routing requests to discovered services, implements performance optimization through usage feedback, and provides automatic fault tolerance with alternative services when servers become unavailable.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that allows users to ping other hosts to check network connectivity and diagnostic information. It enables LLMs to perform network latency tests and host availability checks through a standardized interface.MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that provides standardized tools for AI agents to interact with the Test MCP Feb4 API. It enables LLMs to access API endpoints through asynchronous operations and standardized Model Context Protocol tools.-
- FlicenseNot gradedqualityDmaintenanceA standardized MCP server designed for testing integration with the Des MCP Server Testing API. It allows AI agents to interact with testing endpoints using tools implemented via the Model Context Protocol.-
- AlicenseAqualityDmaintenanceA Model Context Protocol server providing network diagnostic tools for AI agents, including connectivity testing, batch operations, local network info, and pcap analysis.346MIT