Mockmcp

io.github.K-Cupples由 GitHub 帳號 K-Cupples 發布v0.1.0更新於 Oct 24, 2026

Hosted MCP endpoint with realistic fake data for prototyping agents. 12 tools, no setup.

已驗證Streamable HTTP可網頁執行開發者工具資料與分析

概覽

AI 產生的概覽

託管的 MCP 端點，回傳逼真且具確定性的假資料，讓助理不必架後端或準備測試資料就能製作代理工作流程原型。

可以做什麼
列出、取得與建立模擬使用者、商品和訂單，支援分頁、以 id 或種子查詢，訂單可依狀態篩選（建立不會持久化）。記錄並列出模擬分析事件。寄送電子郵件時回傳假的成功訊息，實際不投遞任何內容。執行含排序結果的模擬知識庫搜尋。所有資料以輸入作為種子產生，相同輸入得到相同輸出。
適用情境
適合在真實後端尚不存在時，建置或示範需要使用者、商品、訂單、事件、電子郵件或知識庫資料的代理。也適合教學與快速原型，想要穩定可重現的回應，而不必撰寫測試資料或啟動本機伺服器。
執行需求
遠端 Streamable HTTP 端點；未宣告需要帳號、API 金鑰或環境變數。用戶端需原生支援 Streamable HTTP（範例為 Claude Code、Cursor、Claude Desktop）。免費額度依雜湊後的 IP 與 User-Agent 指紋計算，每分鐘 30 次、每天 500 次請求。
安裝前請注意
所有資料皆為假資料，寫入不會持久化，不應視為真實紀錄。電子郵件工具只回報成功，並未實際投遞。速率限制依雜湊後的 IP 與 User-Agent 指紋計算，候補名單端點會記錄送出的電子郵件地址。README 提到未來將推出付費方案。

安裝

在 SourceWeft 中

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

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

交給代理程式安裝

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

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

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

其他 MCP 客戶端

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

{
  "mcpServers": {
    "mockmcp": {
      "type": "http",
      "url": "https://mockmcp.io/mcp"
    }
  }
}

README

MockMCP

Hosted MCP endpoint returning realistic fake data for prototyping agents. Paste one URL, zero setup.

Live at mockmcp.io — https://mockmcp.io/mcp

Built for devs who want to prototype agent workflows without wiring up a backend, writing fixtures, or standing up a local MCP server. 12 pre-built tools covering the scenarios in most agent tutorials.

Try it

bash
# Initialize a session and get back a session idcurl -i -X POST https://mockmcp.io/mcp \  -H "Content-Type: application/json" \  -H "Accept: application/json, text/event-stream" \  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"0.1"}}}'
# Use the Mcp-Session-Id header in subsequent calls:curl -X POST https://mockmcp.io/mcp \  -H "Content-Type: application/json" \  -H "Accept: application/json, text/event-stream" \  -H "Mcp-Session-Id: <paste-id-here>" \  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"list_users","arguments":{"limit":3}}}'

Connect your client

Claude Code

bash
claude mcp add --transport http mockmcp https://mockmcp.io/mcp

Cursor — add to ~/.cursor/mcp.json:

json
{  "mcpServers": {    "mockmcp": {      "url": "https://mockmcp.io/mcp"    }  }}

Claude Desktop — Settings → Connectors → Add custom connector → paste https://mockmcp.io/mcp as the URL.

No mcp-remote proxy required. All three clients speak Streamable HTTP natively.

Tools

ToolWhat it does
list_usersPaginated list of mock users
get_userOne mock user by id or seed
create_userCreate a mock user (no persistence)
list_productsPaginated list of mock products
get_productOne mock product
list_ordersMock orders with optional status filter
get_orderOne mock order
create_orderCreate a mock order (no persistence)
list_eventsMock analytics events
create_eventRecord a mock event
send_emailReturns fake success, nothing delivered
search_knowledge_baseMock KB search with ranked results

All data is seeded from your inputs — same input, same output.

Limits

Free tier, per hashed IP + User-Agent fingerprint:

  • 30 requests per minute
  • 500 requests per day

Hit the wall? Drop your email at mockmcp.io/waitlist for paid-tier access when it launches.

429 responses carry a structured JSON-RPC error with upgrade_url and retry_after_seconds. Every successful response carries X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, and X-RateLimit-Scope headers.

Run locally

bash
npm installnpm run dev

Server listens on http://localhost:3000. MCP endpoint at /mcp. Without Upstash env vars, rate limiting falls back to an in-memory store (per-process, fine for dev).

Stack

Deploy (for forks)

Targets Node 20+. Build + start are pinned via nixpacks.toml; health checks + restart policy via railway.json.

  1. Fork this repo, push to GitHub.
  2. Railway → New Project → Deploy from GitHub → pick your fork.
  3. Add env vars in Railway → Variables:
VarNotes
UPSTASH_REDIS_REST_URLFrom upstash.com free tier
UPSTASH_REDIS_REST_TOKENPaired with the URL above
PORTRailway sets this automatically
  1. Railway service → Settings → Networking → Custom Domain → paste your domain → follow the DNS instructions.

Health check

GET /health returns {"ok":true}. Railway pings this during deploy.

Waitlist signups

POST /api/waitlist logs a structured JSON line per signup:

json
{"event":"waitlist_signup","email":"[email protected]","at":"2026-04-24T19:33:06.396Z"}

Grep them with railway logs | grep waitlist_signup. Storage-free by design — swap in Resend, a Tally forward, or a DB when the paid tier is live.

License

MIT — see LICENSE.

來源：README.md，提交 3d701a9

工具

0
SourceWeft 尚未讀取此伺服器的工具。

版本歷史

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

評分

已滿足適用檢查項的 85%

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

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分

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

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