SpeedOf.Me

me.speedof由 speedof.me 發布v1.1.4更新於 Oct 24, 2026

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

已驗證STDIO僅桌面安全與監控資料與分析

概覽

AI 產生的概覽

SpeedOf.Me 官方 MCP 伺服器,讓助理執行即時網路測速,並讀取本機歷史記錄中的過往結果。

可以做什麼
透過鄰近的邊緣伺服器執行即時測速,回傳下載、上傳、延遲與抖動數值,可選擇要執行的測試項目、取樣持續時間與整體逾時。依數量或起始時間篩選,讀取本機歷史中的過往結果。以資源形式提供最近結果與目前設定。同一個套件也能作為獨立命令列工具與 Node SDK 使用。
適用情境
適合讓助理依需求檢查目前網路品質、比較不同時間的結果,或在對話中直接回報網速而不必開啟瀏覽器。
執行需求
透過 npm 套件以 stdio 在本機執行,需要 Node.js 18 或更新版本。需要 SpeedOf.Me API 帳號,並透過 SOM_API_SECRET 環境變數提供 API 密鑰;提供免費方案。測速本身需要網路存取。
安裝前請注意
伺服器需要 SOM_API_SECRET 中的 API 密鑰,這屬於憑證,應避免寫入共用的設定檔。測速會消耗 SpeedOf.Me 方案的用量,且每次測試都會連同地理位置、裝置與平台明細記錄到你的儀表板。歷史記錄會寫入本機家目錄下的檔案。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 SpeedOf.Me,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

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.

來源:README.md,提交 b40c5c5

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

2
  1. v1.1.4最新Sep 20, 2026
  2. v1.1.3Sep 16, 2026

評分

已滿足適用檢查項的 40%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。