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 分