MyMCPTools

io.github.shibley由 GitHub 帳號 shibley 發布v0.1.1更新於 Oct 24, 2026

Find MCP servers and check whether they actually respond, via live handshake probes.

已驗證Streamable HTTP可網頁執行網頁搜尋與抓取開發者工具安全與監控

概覽

AI 產生的概覽

一個託管、唯讀的 MCP 伺服器，用來檢索 MCP 伺服器目錄，並透過即時握手探測確認所列伺服器是否真的能回應。

可以做什麼
  • 依關鍵字、分類、用戶端整合、安裝類型或官方狀態檢索 MCP 伺服器目錄，並列出分類與整合及其數量。
  • 查看單一伺服器的完整條目：描述、作者、安裝指令、儲存庫、支援的用戶端與目前探測結論。
  • 查詢單一伺服器或整個目錄的即時狀態：結論、工具數量、握手延遲、協定版本與最近正常時間。
  • 查看探測歷史與每日上線率走勢，並列出重建的故障事件。
  • 追蹤相鄰探測間的工具結構與協定版本漂移，並取得整體目錄健康統計。
適用情境
適合在挑選要加入的 MCP 伺服器時，確認遠端伺服器確實可連線；也適合監控已依賴的伺服器是否發生故障或破壞性工具變更。依分類或用戶端瀏覽目錄時同樣實用。
執行需求
需要連線到 mymcptools.com 的遠端 Streamable HTTP 端點，無需 API 金鑰或驗證。另有本機 stdio 轉接器，但尚未發布到 npm，需以 Node.js 18+ 從原始碼建置；可用 MYMCPTOOLS_MCP_URL 覆寫上游端點。
安裝前請注意
唯讀且無狀態，不索取任何憑證。探測結論只涵蓋遠端端點：目錄中大多數條目為本機伺服器，會顯示為 UNPROBEABLE，意思是無法遠端檢查，而非已損壞。上線率與漂移資料來自營運方自身的探測，並非獨立驗證。

安裝

在 SourceWeft 中

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

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.shibley%2Fmymcptools/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "mymcptools": {
      "type": "http",
      "url": "https://mymcptools.com/api/mcp"
    }
  }
}

README

MyMCPTools MCP Server

An MCP server for finding other MCP servers — and, more usefully, for checking whether the one you are about to recommend is actually reachable.

Every uptime figure it returns comes from a real MCP handshake against the server's remote endpoint, not from self-reported metadata in a README.

Backed by mymcptools.com. No API key required.

Install

Remote endpoint (recommended — nothing to install)

The server is hosted. If your client speaks Streamable HTTP, point it straight at:

https://mymcptools.com/api/mcp

Stateless, read-only, no auth, no API key. This is also the entry published to the official MCP Registry as io.github.shibley/mymcptools.

Local stdio adapter

The code in this repo is a thin stdio adapter over that same endpoint, for clients that don't speak Streamable HTTP yet. It is not on npm yet, so build it from source (Node.js 18+):

bash
git clone https://github.com/shibley/mymcptools-mcp-server.gitcd mymcptools-mcp-servernpm install && npm run build

Then point your client at the built entrypoint:

json
{  "mcpServers": {    "mymcptools": {      "command": "node",      "args": ["/absolute/path/to/mymcptools-mcp-server/dist/index.js"]    }  }}

Add that to claude_desktop_config.json (Claude Desktop), .cursor/mcp.json (Cursor), or your client's equivalent.

Set MYMCPTOOLS_MCP_URL to override the upstream endpoint the adapter talks to.

Tools

ToolWhat it answers
search_mcp_serversWhich servers match this keyword, category, client integration or install type?
get_mcp_serverFull entry for one server: install command, repo, supported clients, current probe verdict.
get_server_statusIs this server reachable right now? Verdict, exposed tool count, handshake latency, negotiated protocol version.
get_server_historyTrailing probe history and a daily uptime sparkline for one server.
list_server_incidentsReconstructed outages — contiguous runs of failed probes, with start, end and duration.
list_schema_driftWhich servers added, removed or changed tools between probes. Useful for spotting breaking changes.
list_categoriesEvery category and client integration, with counts. Returns the valid slugs for the filters above.
get_catalog_statsPopulation-level health: verdict breakdown, transport mix, latency percentiles.

What the probe data does and does not cover

Worth stating plainly, because the numbers are easy to misread:

  • The catalog carries ~2,700 entries, but only ~44 are probeable — that is, they publish a remote endpoint something can actually connect to.
  • The rest are local-only servers (stdio, run via npx or docker on your machine). There is no remote endpoint to handshake against, so they are reported as UNPROBEABLE rather than assigned a made-up status. For those, get_mcp_server falls back to a static repo-freshness signal.
  • UNPROBEABLE therefore means "not remotely checkable", not "broken".

So treat the live-verification tools as high-confidence for remote/hosted servers, and treat the catalog entry itself as the useful part for local ones.

Verdicts

VerdictMeaning
GOODHandshake succeeded and the server listed its tools.
WARNReachable, but something was off — slow handshake or a degraded response.
AUTH_REQUIREDEndpoint is live but needs credentials before it will list tools.
DOWNEndpoint is published but the handshake failed.
UNPROBEABLENo remote endpoint to probe — typically a local stdio server.

Development

bash
npm installnpm run build

Smoke-test the built server over stdio:

bash
printf '%s\n%s\n%s\n' \  '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"t","version":"1"}}}' \  '{"jsonrpc":"2.0","method":"notifications/initialized"}' \  '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}' \  | node dist/index.js

License

MIT

來源：README.md，提交 9159ce4

工具

8

search_mcp_servers

Search MCP servers

Search the MyMCPTools catalog of Model Context Protocol servers. Filter by free-text query, category slug, integration slug (claude-desktop, cursor, vs-code, ...), install type, or official status. Set only_verified to restrict to servers that answered a live MCP handshake on the most recent probe. Results carry the live verdict for each server.

輸入參數limitquerycategoryofficialintegrationinstall_typeonly_verified

get_mcp_server

Get one MCP server

Full catalog entry for one MCP server by slug: description, author, install command, repo, supported clients, current probe verdict, static repo-freshness signal for local servers, and related servers in the same categories.

輸入參數slug必填

get_server_status

Get live MCP server status

Current live-probe status for one server: verdict (GOOD / WARN / AUTH_REQUIRED / DOWN / UNPROBEABLE), exposed tool count, handshake latency, negotiated protocol version, remote endpoint, and when it was last seen healthy. Omit the slug to get the catalog-wide verdict summary instead.

輸入參數slug

get_server_history

Get MCP server uptime history

Trailing probe history for one server plus a daily uptime sparkline — the reliability signal behind the badge on mymcptools.com. Returns per-day uptime buckets and the raw probe points (timestamp, verdict, latency).

輸入參數daysslug必填limit

list_server_incidents

List MCP server outage incidents

Reconstructed outage incidents (contiguous runs of failed probes) across the catalog, newest first. Each incident has a start, an end (or ongoing), a duration and the failure reason. Filter to one server with slug, or to open outages with status='ongoing'.

輸入參數sluglimitstatus

list_schema_drift

List MCP tool-schema drift

Tool-schema and protocol-version drift events detected between successive probes — which servers added, removed or changed tools, and when. Use this to spot breaking changes in a server you depend on. Newest first.

輸入參數sluglimit

list_categories

List catalog categories

Every category and client integration in the MyMCPTools catalog, with the number of servers in each. The slugs returned here are the valid category and integration filter values for catalog searches.

無需輸入參數。

get_catalog_stats

Get catalog-wide health stats

Aggregate health of the whole MCP population: verdict breakdown, share of probeable servers actually serving, transport mix, handshake latency percentiles, tool counts and probe freshness. This is the 'how healthy is MCP right now?' headline number.

無需輸入參數。

版本歷史

1
  1. v0.1.1最新Sep 16, 2026

評分

已滿足適用檢查項的 100%

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

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分