Internet Speed Test

Created By
inventer-deva year ago
The MCP Internet Speed Test is a specialized Model Context Protocol (MCP) server that enables AI models and agents to perform internet speed measurements.
Overview

What is MCP Internet Speed Test?

The MCP Internet Speed Test is an experimental Model Context Protocol (MCP) server designed to enable AI models and agents to measure and analyze internet speed metrics such as download and upload speeds, latency, and jitter.

How to use MCP Internet Speed Test?

To use the MCP Internet Speed Test, install the required Python version and the uv package manager. You can run the server using the uvx command and configure it in your MCP client settings.

Key features of MCP Internet Speed Test?

  • Download Speed Testing: Measure download bandwidth.
  • Upload Speed Testing: Measure upload bandwidth with configurable file sizes.
  • Latency Testing: Measure network latency to various servers.
  • Jitter Analysis: Calculate network jitter by analyzing latency variations.
  • Comprehensive Reporting: Provide detailed JSON-formatted reports.

Use cases of MCP Internet Speed Test?

  1. Testing internet speed for AI applications.
  2. Analyzing network performance for research purposes.
  3. Integrating with AI models to provide real-time network metrics.

FAQ from MCP Internet Speed Test?

  • What is the Model Context Protocol (MCP)?

MCP is a standardized way for AI models to interact with external tools and data sources, facilitating real-world capabilities.

  • Is this project stable for production use?

No, this is an experimental version and may have limitations.

  • How can I contribute to the project?

You can contribute by opening issues or submitting pull requests on the project's GitHub repository.

Server Config

{
  "mcpServers": {
    "internet-speed-test": {
      "command": "uvx",
      "args": [
        "/path/to/mcp-internet-speed-test"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
inventer-dev
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago