# mock-server/mockserver-monorepo

MockServer is an HTTP(S) mock server and proxy for testing that lets you mock APIs, inspect and modify live traffic, and inject failures. It supports HTTP/1.1, HTTP/2, gRPC, WebSockets, TCP and more on a single port, with additional support for HTTP/3, message brokers, and AI/LLM APIs.

Repository: https://github.com/mock-server/mockserver-monorepo
Canonical: https://ross.abutalabs.com/products/mockserver-monorepo
Homepage: https://www.mock-server.com
Language: Java
License: Apache-2.0
License Family: permissive
Topics: mock-server, proxy, java-client, javascript-client, node-module, node-client, ruby-client, homebrew, grunt-plugin, ai, chaos-engineering, llm, mcp, python, testing
Last push: 2026-08-26T23:08:59+00:00

## Health v2 (maintenance only)
Score: 99/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 98, longevity 100
- inputs: {"age_days": 4936, "days_push": 7, "days_rel": 16, "gap_med": 8.5, "n_releases_24m": 9}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 4953, forks 1115 (observed 2026-08-28T04:09:03.729383+00:00)

## What it is
MockServer is an open-source HTTP(S) mock server and proxy for testing that can mock APIs, record and inspect live traffic, and inject failures for chaos testing. It supports HTTP/1.1, HTTP/2, HTTP/3, gRPC, WebSockets, TCP, message brokers, and AI/LLM APIs on a single port, with clients for Java, JavaScript, Ruby, and Python.

## Use cases
- mock third-party APIs my tests depend on
- record and replay live HTTP traffic for debugging
- inject latency and errors to test service resilience
- mock OpenAI or Anthropic LLM APIs in tests
- generate mocks from an OpenAPI specification
- verify which requests my service sent and in what order

## When to choose
- you need deterministic, isolated tests against unavailable or in-development dependencies
- you want one tool that mocks many protocols including gRPC, WebSockets, and message brokers
- you need chaos engineering or traffic recording/proxying alongside mocking

## When to avoid
- you only need simple static JSON fixtures with no matching or verification logic
- you want a lightweight in-process mocking library rather than a standalone server

## Facets
- artifact type: service
- maturity: active
- function: mock-api, http-server, proxy, testing, e2e-testing, mcp
- domain: testing, developer-tools, apis
- platform: self-hosted, jvm, python, cli
- tags: mock-server, chaos-engineering, llm-mocking, grpc, websockets, openapi, traffic-recording, devops, docker, nodejs

## Member repositories
- mock-server/mockserver-monorepo (main) score 99

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:09:03.729383+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T18:17:51.244862+00:00, confidence not recorded.
  - readme: https://github.com/mock-server/mockserver-monorepo (fetched 2026-08-28T04:09:03.729383+00:00, sha 762e89666dc9)
  - homepage: https://www.mock-server.com (fetched 2026-08-29T08:59:16.855945+00:00, sha 4a5d2702ddb3)
- Data as of 2026-08-30T08:39:29.467469+00:00.