mcp-internet-speed-test
Prueba de velocidad de Internet MCP
⚠️ Versión experimental
Esta es una implementación experimental de un servidor de Protocolo de Contexto de Modelo (MCP) para pruebas de velocidad de internet. Permite que los modelos y agentes de IA midan, analicen e informen métricas de rendimiento de la red mediante una interfaz estandarizada.
Related MCP server: Test MCP Feb4 MCP Server
¿Qué es MCP?
El Protocolo de Contexto de Modelo (MCP) proporciona una forma estandarizada para que los Modelos de Lenguaje Grandes (LLM) interactúen con herramientas externas y fuentes de datos. Considérelo como el "USB-C para aplicaciones de IA": una interfaz común que permite a los sistemas de IA acceder a capacidades e información del mundo real.
Características
Prueba de velocidad de descarga : mide el ancho de banda de descarga
Prueba de velocidad de carga : mida el ancho de banda de carga con tamaños de archivos configurables
Prueba de latencia : mide la latencia de la red en varios servidores
Análisis de fluctuación : Calcule la fluctuación de la red analizando las variaciones de latencia
Informes completos : proporcione informes detallados en formato JSON
Instalación
Prerrequisitos
Python 3.12 o superior
Gestor de paquetes uv (recomendado)
Opción 1: Usar uvx (recomendado)
El comando uvx es una forma conveniente de ejecutar paquetes de Python directamente sin instalación explícita:
# Run the MCP server directly
uvx /path/to/mcp-internet-speed-testOpción 2: Usar 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-testConfiguración
Para utilizar este servidor MCP con Claude Desktop u otros clientes MCP, agréguelo a su archivo de configuración de MCP.
Configuración del escritorio de Claude
Edite su archivo de configuración MCP de Claude Desktop:
{
"mcpServers": {
"mcp-internet-speed-test": {
"command": "uv",
"args": [
"--directory",
"/ABSOLUTE/PATH/TO/mcp-internet-speed-test",
"run",
"main.py"
]
}
}
}Herramientas API
La prueba de velocidad de Internet MCP proporciona las siguientes herramientas:
measure_download_speed: Mide el ancho de banda de descarga (en Mbps)measure_upload_speed: Mide el ancho de banda de carga (en Mbps)measure_latency: mide la latencia de la red (en ms)measure_jitter: mide la fluctuación de la red analizando las variaciones de latenciarun_complete_test: ejecuta todas las pruebas y proporciona un informe completo
Solución de problemas
Si tiene problemas para conectarse al servidor MCP:
Asegúrese de que la ruta en su configuración de MCP sea correcta
Comprueba que tienes los permisos necesarios para el directorio
Verifique que Python 3.12+ esté instalado y en su PATH
Asegúrese de que los paquetes
mcp[cli]yrequestsestén instalados
Desarrollo
Este es un proyecto experimental y se agradecen las contribuciones. Para contribuir:
Abrir un problema o enviar una solicitud de extracción
Licencia
Este proyecto está licenciado bajo la licencia MIT: consulte el archivo de LICENCIA para obtener más detalles.
Expresiones de gratitud
Mantenedores del marco MCP para estandarizar las interacciones de las herramientas de IA
La comunidad del Protocolo de Contexto Modelo para documentación y ejemplos
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