Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Hosted MCP endpoint with realistic fake data for prototyping agents. 12 tools, no setup.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mockmcp.io/mcpRun this in your terminal
claude mcp add --transport http mockmcp https://mockmcp.io/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mockmcp": {
"url": "https://mockmcp.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"mockmcp": {
"type": "http",
"url": "https://mockmcp.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mockmcp.io/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account K-Cupples, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 7 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, aamio rendezvous
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Meet an agent you have not met, exchange messages that expire, and prove it happened. No account.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Hosted MCP endpoint returning realistic fake data for prototyping agents. Paste one URL, zero setup.
Live at [mockmcp.io](https://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.
# Initialize a session and get back a session id
curl -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"}}}'
curl -X POST https://mockmcp.io/mcp \ -H "Content-Type: application/json" \ -H "Accept: application/json, text/event-stream" \ -H "Mcp-Session-Id: " \ -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"list_users","arguments":{"limit":3}}}'
Claude Code
claude mcp add --transport http mockmcp https://mockmcp.io/mcp
Cursor — add to ~/.cursor/mcp.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.
| Tool | What it does |
|---|---|
list_users | Paginated list of mock users |
get_user | One mock user by id or seed |
create_user | Create a mock user (no persistence) |
list_products | Paginated list of mock products |
get_product | One mock product |
list_orders | Mock orders with optional status filter |
get_order | One mock order |
create_order | Create a mock order (no persistence) |
list_events | Mock analytics events |
create_event | Record a mock event |
send_email | Returns fake success, nothing delivered |
search_knowledge_base | Mock KB search with ranked results |
All data is seeded from your inputs — same input, same output.
Free tier, per hashed IP + User-Agent fingerprint:
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.
npm install
npm 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).
@modelcontextprotocol/sdk — MCP server + Streamable HTTP transporthttp — no framework overhead, clean shutdown@faker-js/faker — deterministic fake data via seeds@upstash/ratelimit + @upstash/redis — sliding-window rate limitingzod — tool input validationTargets Node 20+. Build + start are pinned via nixpacks.toml; health checks + restart policy via railway.json.
| Var | Notes |
|---|---|
UPSTASH_REDIS_REST_URL | From upstash.com free tier |
UPSTASH_REDIS_REST_TOKEN | Paired with the URL above |
PORT | Railway sets this automatically |
GET /health returns {"ok":true}. Railway pings this during deploy.
POST /api/waitlist logs a structured JSON line per signup:
{"event":"waitlist_signup","email":"alice@example.com","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.
MIT — see LICENSE.