Mockserver MCP server
com.mock-server/mockserver·v9.2.0·5.0k starsMock, record/replay, verify and chaos-test any HTTP, REST, gRPC or LLM dependency over MCP.
not scanned yet
5.0k stars
Reviews
Write oneNobody has reviewed Mockserver yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Mockserver tools
No tool declarations could be read from the package source. They show once the server is installed.
How Mockserver compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 93/100
- higher than 96% of 4,460 AI and agents servers
- GitHub stars
- 4,980
- more than 96% of 2,711 AI and agents servers
Release history: 4 versions in the registry since 2026-09-15, latest 2026-10-27, typically one every 6 days.
Install Mockserver in Claude Code, Cursor or VS Code
claude mcp add mockserver -- docker run -i --rm docker.io/mockserver/mockserver:9.2.0
What the publisher says
From the Mockserver repository's README, as published. We do not edit it. Read it on GitHub
MockServer
MockServer is an HTTP(S) mock server and proxy for testing. It does three things:
- Mock the APIs your application depends on, so you can develop and test against systems that are unavailable, incomplete, or hard to reproduce.
- Proxy real traffic to record, inspect, and modify requests and responses in flight — and pause them at interactive proxy breakpoints to step through, edit, or abort each exchange like a debugger for network traffic.
- Chaos engineering — make dependencies misbehave on demand, injecting latency, dropped connections, and errors to test how your application copes when the systems it relies on degrade or fail.
Speaks every protocol your stack uses. HTTP/1.1 & HTTPS, HTTP/2, gRPC & gRPC-Web, WebSockets and raw TCP are auto-detected from the first bytes of each connection, so one MockServer port handles them all with no per-protocol configuration. Beyond that core: HTTP/3 (QUIC — experimental, on its own UDP port), JSON-RPC for MCP/A2A mocking, AsyncAPI-driven message-broker testing against external Kafka and MQTT brokers, and mocked AI/LLM chat-completion APIs (OpenAI, Anthropic, Gemini, Bedrock, Azure OpenAI, Ollama).
Main Features
- Mock any API — HTTP/1.1, HTTPS, HTTP/2, HTTP/3, gRPC, gRPC-Web, JSON-RPC, WebSockets, raw TCP, and message brokers (Kafka, MQTT). Match requests on method, path, query, headers, cookies and body (JSON, XML, JSONPath, XPath, regex, OpenAPI) and return configured responses.
- Proxy & record — port forwarding, web (HTTP) proxy, HTTPS tunneling (CONNECT) and SOCKS, with full visibility of even TLS-encrypted traffic.
- Dynamic responses — response templating (Velocity, Mustache, JavaScript), class/closure callbacks and webhooks.
- OpenAPI — generate expectations directly from an OpenAPI/Swagger specification.
- Verification — assert which requests were received, in what order, and how many times.
- Chaos & resilience testing — inject latency, dropped/slow connections and failures to test how your system copes with a misbehaving dependency.
- LLM / AI mocking — mock chat-completion APIs for OpenAI, Anthropic, Gemini, Bedrock, Azure OpenAI and Ollama (including streaming), plus a built-in MCP server for AI coding assistants.
- Live dashboard — watch requests, expectations and logs in real time at /mockserver/dashboard.
- Clients & integrations — Java, JavaScript/Node, Python and Ruby clients, plus JUnit and Spring support.
- Run anywhere — Docker, Helm/Kubernetes, JAR or WAR, with optional clustered state for multi-instance deployments.
See the changelog for what has shipped in each version.
Getting started in 60 seconds
Run MockServer with Docker, then mock an endpoint and call it:
# 1. Start MockServer
docker run -d --rm -p 1080:1080 mockserver/mockserver
# 2. Mock an endpoint: GET /hello -> 200 "Hello World"Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Mockserver: common questions
- Is Mockserver MCP server safe?
- Yes, by our scan: it is graded A (93/100). Read the Mockserver safety report
- How do I install Mockserver?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Mockserver need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Mockserver maintained?
- The last commit was 32 days ago (2026-10-03). The latest release is v9.2.0.
- What can I use instead of Mockserver?
- Servers from other publishers that do the same job: CHAP Coordinator MCP server, TradeOS (test) MCP server and agent-device MCP server.
- How does Mockserver compare with other AI and agents MCP servers?
- safety score 93/100 (higher than 96% of 4,460 AI and agents servers); github stars 4,980 (more than 96% of 2,711 AI and agents servers). Full comparison.
Alternatives to Mockserver
Same job from other publishers: the closest match first, then the best rated.
- CHAP CoordinatorAuditable records of human decisions over AI agent work. Approvals, edits, overrides, escalations.not reviewedEstablishedA
- TradeOS (test)[TEST] TradeOS MCP bridge: ticker search, My Agent, chart TA, macro news. npm or HTTP.not reviewedEstablishedC
- agent-deviceOpen source device layer for AI agents: control mobile, web, TV, and desktop apps over MCPnot reviewedWidely usedA
- Pm Claude Skills1310 professional Agent Skills + workflow recipes — searchable & fetchable over MCP.not reviewedEstablishedA
- Watch SkillWatch video and live sessions, keep timestamped evidence, and verify an agent's own work.not reviewedEstablishedB