SpeedOf.Me

me.speedofPublished by speedof.mev1.1.4Updated Oct 24, 2026

Official SpeedOf.Me server - Accurate speed tests via over 200 global edge servers with analytics.

VerifiedSTDIODesktop onlySecurity & MonitoringData & Analytics

Overview

AI-generated overview

Official SpeedOf.Me MCP server that lets an assistant run live internet speed tests and read past results from local history.

What you can do
Run a live speed test against nearby edge servers and get download, upload, latency and jitter figures in Mbps and milliseconds, optionally choosing which tests to run, sample sustain time and an overall timeout. Read previous results from local history, filtered by count or start date. Expose recent results and current configuration as resources. The same package also runs as a standalone CLI and a Node SDK.
When to use it
Useful when you want an assistant to check the current connection quality on demand, compare results over time, or report speeds in a conversation without opening a browser.
Requirements
Runs locally over stdio via the npm package, so Node.js 18 or newer is needed. A SpeedOf.Me API account and an API secret supplied in the SOM_API_SECRET environment variable are required; a free tier is available. Network access is needed for the tests themselves.
Before you install
The server requires an API secret in SOM_API_SECRET, which is a credential and should be kept out of shared configuration files. Tests consume usage against your SpeedOf.Me plan, and every test is recorded in your dashboard with geographic, device and platform breakdowns. History is written locally to a file in your home directory.

Installation

In SourceWeft

  1. Open SpeedOf.Me in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

SpeedOf.Me MCP Server

Official MCP server for SpeedOf.Me. Lets an AI agent run a real internet speed test and read the result: download, upload, latency and jitter, measured against 130+ global edge servers.

[npm version] [MCP Registry] [GitHub MCP Registry] [Node]

"How fast is my connection right now?"→ 187.4 Mbps down / 41.2 Mbps up / 11 ms latency / 1.8 ms jitter (San Jose)

Tools

ToolWhat it does
run_speed_testRuns a live speed test and returns download, upload, latency and jitter
get_test_historyReturns previous results from local history
ResourceContents
speedofme://historyRecent test results (JSON)
speedofme://configCurrent configuration and status

Quick start

1. Get a free API secret

Register, then open Integrations and generate a secret.

2. Add the server to your MCP client

json
{  "mcpServers": {    "speedofme": {      "type": "stdio",      "command": "npx",      "args": ["-y", "@speedofme/mcp"],      "env": {        "SOM_API_SECRET": "SOM_SECRET_xxx"      }    }  }}

Claude Code, one command:

bash
claude mcp add speedofme --env SOM_API_SECRET=SOM_SECRET_xxx -- npx -y @speedofme/mcp

VS Code (Copilot) uses servers instead of mcpServers in .vscode/mcp.json; the rest of the block is identical. Cursor, Windsurf, Zed, Cline, Continue, JetBrains and Goose all take the JSON above. Client-specific configs and agent-framework examples (LangChain, LlamaIndex, AutoGen, CrewAI, Semantic Kernel) are in the integration docs.

3. Restart the client and ask for a speed test.

Tool reference

run_speed_test

ParameterTypeDefaultDescription
testsstring[]allWhich tests to run: download, upload, latency
sustainTimenumber6Seconds to sustain each sample (1-8). Lower is faster, higher is more accurate
testTimeoutnumber300Wall-clock cap for the whole run, in seconds. 0 disables, min 30, max 1800

The tool replies with formatted text. The underlying result looks like this:

json
{  "testId": "abc123",  "download": 150.5,  "upload": 45.2,  "latency": 12,  "jitter": 2.3,  "testServer": "San Jose",  "timestamp": "2026-08-18T10:30:00Z"}

Speeds are Mbps, latency and jitter are milliseconds.

get_test_history

ParameterTypeDefaultDescription
limitnumber10Maximum number of results
sincestringnoneISO date string. Only results after this time

History is stored locally in ~/.speedofme/history.json, capped at 1 MB (roughly 2,600 results).

Also a CLI

The same package runs standalone, no MCP client required:

bash
SOM_API_SECRET=SOM_SECRET_xxx npx -y @speedofme/mcp --progress   # human readableSOM_API_SECRET=SOM_SECRET_xxx npx -y @speedofme/mcp --json       # for scriptsnpx -y @speedofme/mcp history --limit 5                          # past resultsnpx -y @speedofme/mcp --help

And as a Node SDK:

javascript
const { SpeedTest } = require('@speedofme/mcp');
const test = new SpeedTest({ apiSecret: process.env.SOM_API_SECRET });const result = await test.run();          // { download, upload, latency, jitter, ... }

Full CLI and SDK options are documented on npm.

How the measurement works

SpeedOf.Me has measured what we call Real-World Speed the same way since 2011. Rather than blasting a fixed payload, the test downloads progressively larger samples, starting at 128 KB, until one takes longer than the sustain time (6 seconds by default), and reports the rate of that final sample. Upload works the same way in reverse, and latency and jitter come from 10 round-trip samples. Tests run against the nearest of 130+ edge locations, so an agent gets the same number a person would see in the browser.

Every test also lands in your dashboard with geographic, device and platform breakdowns, and usage against your plan.

Details: how it works.

Requirements

  • Node.js 18 or newer
  • A SpeedOf.Me API account and secret (free tier available)

About this repository

This repo is the home of the MCP server: documentation, the registry entry (server.json) and the issue tracker. The server itself is distributed as the @speedofme/mcp npm package and its source is not published here.

Found a bug or want a tool added? Open an issue, or email [email protected].

Links

License

The @speedofme/mcp package is proprietary software of Speed of Me, LLC. Unauthorized copying or redistribution is prohibited. The documentation in this repository is provided for use with the SpeedOf.Me API.

Source: README.md at commit b40c5c5

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.1.4LatestSep 20, 2026
  2. v1.1.3Sep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.