
Mockmcp
io.github.K-CupplesPublished by GitHub account K-Cupplesv0.1.0Updated Oct 24, 2026
Hosted MCP endpoint with realistic fake data for prototyping agents. 12 tools, no setup.
Overview
A hosted MCP endpoint that returns realistic, deterministic fake data so assistants can prototype agent workflows without a backend or fixtures.
- What you can do
- List, fetch and create mock users, products and orders, with pagination, id or seed lookup and status filters for orders (creates are not persisted). Record and list mock analytics events. Return a fake success for sending email, with nothing actually delivered. Run a mock knowledge-base search with ranked results. All data is seeded from the inputs, so the same input gives the same output.
- When to use it
- Useful when building or demoing an agent that needs user, product, order, event, email or knowledge-base data before a real backend exists. Good for tutorials and quick prototypes where you want stable, repeatable responses without writing fixtures or running a local server.
- Requirements
- A remote Streamable HTTP endpoint; no account, API key or environment variables are declared. Clients must support Streamable HTTP natively (Claude Code, Cursor, Claude Desktop are shown). The free tier is limited to 30 requests per minute and 500 per day per hashed IP and User-Agent fingerprint.
Installation
In SourceWeft
- Open Mockmcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.K-Cupples%2Fmockmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"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
Connect your client
Claude Code
Cursor — add to ~/.cursor/mcp.json:
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
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
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
@modelcontextprotocol/sdk— MCP server + Streamable HTTP transport- Raw Node
http— no framework overhead, clean shutdown @faker-js/faker— deterministic fake data via seeds@upstash/ratelimit+@upstash/redis— sliding-window rate limitingzod— tool input validation
Deploy (for forks)
Targets Node 20+. Build + start are pinned via nixpacks.toml; health checks + restart policy via railway.json.
- Fork this repo, push to GitHub.
- Railway → New Project → Deploy from GitHub → pick your fork.
- Add env vars in Railway → Variables:
- 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:
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.
Source: README.md at commit 3d701a9
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts