mockd
Related Servers
Alternatives to mockd
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceAn Intelligent Model Context Protocol server that generates mock servers from OpenAPI specifications, featuring advanced logging, performance analytics, and server discovery for AI-assisted API development.MIT
- AlicenseNot gradedqualityBmaintenanceA lightweight mock MCP server for local testing and resilience experiments, providing predictable tool responses with simulated latency and errors.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables instant creation of mock API servers from OpenAPI specs or natural language descriptions, with built-in fake data generation, CRUD endpoints, and configurable delays/errors for testing.-
- AlicenseBqualityDmaintenanceA mock MCP server for testing MCP client implementations and development workflows. Supports tools, prompts, and resources across multiple transport protocols (stdio, HTTP, SSE).1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for API request automation and testing, with multi-project workspaces, environment profiles, OAuth2 support, WebSocket testing, assertions, and history auditing.6 npm5MIT
- AlicenseAqualityCmaintenanceAn MCP server for interacting with MockServer, enabling AI assistants to create mock HTTP expectations, verify requests, clear state, and manage MockServer instances programmatically.643 npm1MIT
TDQS
Scored across 18 tools
Most tools target distinct resources (mocks, chaos, state, context, workspace), but get_mock_invocations, get_request_logs, and verify_mock all deal with call history/verification and may be confused. Overall, the separation is reasonable.
All tool names follow a consistent verb_noun pattern (set_, get_, reset_, manage_, import_, export_, verify_, clear_). The manage_ prefix is uniformly applied to multi-action tools, making the naming predictable.
Eighteen tools is on the higher end but appropriate for a mock server covering chaos testing, stateful resources, verification, and server administration. Several tools (manage_state, manage_mock, manage_custom_operation) bundle many sub-operations, which keeps the count reasonable.
The tool surface covers the full mock-server lifecycle: creation/management, request verification, stateful behavior, chaos injection, monitoring, and environment/workspace controls. Missing operations can generally be performed via existing tools with action parameters.