MCP.Market

SpeedOf.Me MCP server

by speedof.me·me.speedof/speed-test·v1.1.4·1 stars

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

B83/100grade B
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
New

1 stars

Reviews

Write one

Nobody has reviewed SpeedOf.Me yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

SpeedOf.Me tools (2, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • get_test_history

    Get historical speed test results from local storage.

  • run_speed_testwrite action

    Run an internet speed test to measure download speed, upload speed, latency, and jitter. Results are saved to local history.

Public scan report

scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it

no findings
  • Code scan5 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 26 days ago15/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How SpeedOf.Me compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 48,243 servers
Tools
2
the typical server has 7
Tools that change things
50%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 65% of 28,706 servers

What its tools let an agent do: 1 read · 1 run or deploy

Release history: 2 versions in the registry since 2026-08-31, latest 2026-09-19, typically one every 19 days.

Install SpeedOf.Me in Claude Code, Cursor or VS Code

Runs npx -y @speedofme/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add speed-test -- npx -y @speedofme/mcp
Add to Cursor

What the publisher says

From the SpeedOf.Me repository's README, as published. We do not edit it. Read it on GitHub

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.

"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

Quick start

1. Get a free API secret

Register, then open Integrations and generate a secret.

2. Add the server to your MCP client

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

Claude Code, one command:

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

runspeedtest

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

{
  "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.

gettesthistory

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:

SOM_API_SECRET=SOM_SECRET_xxx npx -y @speedofme/mcp --progress   # human readable
SOM_API_SECRET=SOM_SECRET_xxx npx -y @speedofme/mcp --json       # for scripts
npx -y @speedofme/mcp history --limit 5                          # past results
npx -y @speedofme/mcp --help

And as a Node SDK:

const { SpeedTest } = require('@speedofme/mcp');

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

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

SpeedOf.Me: common questions

Is SpeedOf.Me MCP server safe?
Mostly: it is graded B (83/100). Read the SpeedOf.Me safety report
How do I install SpeedOf.Me?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does SpeedOf.Me need an API key?
Yes. The registry entry asks for SOM_API_SECRET.
Is SpeedOf.Me maintained?
The last commit was 47 days ago (2026-09-19). The latest release is v1.1.4.
How does SpeedOf.Me compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,243 servers); tools 2 (the typical server has 7); tools that change things 50% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.