hoverfly-mcp-server
Hoverfly MCP Server is a Spring Boot-based Model Context Protocol (MCP) server that exposes Hoverfly’s mock-management capabilities as MCP tools, enabling AI assistants to start/stop Hoverfly, create/clear/list mocks, fetch status/version, and download simulation data (typically via a Docker deployment with mounted persistence).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
TLS/auth/authorization details are not described in the README content provided; therefore, security posture is uncertain. The tool can start/stop a mock server and manage mocks, which is sensitive if exposed to untrusted users. Treat the MCP endpoint as privileged; restrict network access and control exposure (e.g., run only locally or behind an authenticated reverse proxy). No secret-management guidance is provided, but no obvious secret-in-code/log claims are present in the provided documentation.
⚡ Reliability
Best When
You want an MCP-capable assistant to manage Hoverfly mocks interactively for development/testing, using Docker with a writable mounted volume for simulation persistence.
Avoid When
You need strong authentication/authorization, documented rate limits, or formal reliability/security assurances from the package documentation.
Use Cases
- • Using an AI assistant to automatically set up request/response mocks for unavailable third-party APIs
- • Local development and integration testing with deterministic simulated external services
- • Programmatic control of Hoverfly mock lifecycle (start, add mocks, list, clear, stop)
- • Exporting/persisting Hoverfly simulations across container restarts
Not For
- • Production-grade multi-tenant API mocking behind strict enterprise access controls (no auth described)
- • Workloads requiring guaranteed uptime/SLA or clearly documented operational reliability
- • Environments where writing to a mounted persistence directory is disallowed
Interface
Authentication
The provided documentation does not describe any authentication/authorization for the MCP server or tool endpoints. If the MCP server is exposed beyond localhost, access control should be handled externally (e.g., network policies, reverse proxy, firewall).
Pricing
No pricing information provided (appears to be an open-source self-hosted tool).
Agent Metadata
Known Gotchas
- ⚠ Tool inputs rely on Hoverfly JSON definitions (e.g., RequestResponsePair); malformed JSON will likely fail tool execution (no explicit schema/examples beyond general description).
- ⚠ Persistence depends on a mounted writable volume at /opt/hoverfly-mcp/simulation-data; if volume is not mounted or not writable, simulation persistence/export may not behave as expected.
- ⚠ Auto-load behavior on startup may surprise agents if the most recent simulation file differs from what the agent expects; ensure consistent simulation state (use download/clear tools as needed).
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for hoverfly-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.