MockHero
✓ VerifiedDescription
MockHero generates realistic, relational synthetic test data from a JSON schema, plain-English prompt, or template — 156 field types, 22 locales, JSON/CSV/SQL output, with valid foreign keys across related tables (orders reference real user IDs, reviews link to real products). Built for AI coding agents and developers who need seed data, fixtures, demo data, or QA datasets without hand-writing repetitive faker scripts. Free keyless preview: generate up to 100 records per request with an explicit table schema, no signup or API key required. For larger volumes or plain-English prompt generation, get an API key by creating a loginless Polar checkout (no account needed) — 500 free records/day, then $0.001 per 100 records billed monthly. Polar is the Merchant of Record. Deterministic seeds make output reproducible across runs. Locale-aware data (names, phone formats, addresses) covers 22 locales.
What our measurements say
MockHero is a remote MCP server published at mockhero.dev. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 1,468 ms, a delay an agent will notice. It offers a narrow, focused set of 6 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool names are descriptive and align with their purposes (e.g., 'detect_schema' clearly indicates schema conversion).
- Descriptions explicitly state usage conditions (free vs. API key required) and output formats.
- Comprehensive coverage of data generation needs (schema, templates, field types).
Weaknesses
- Some tool names lack specificity (e.g., 'estimate_agent_usage' is ambiguous without context).
- Parameter details in descriptions are sparse (e.g., 'generate_test_data' lacks explicit required schema fields).
- Potential overlap between 'generate_test_data' and 'generate_from_template' may confuse agents.
estimate_agent_usage— Tool name is vague; 'agent-plan cost' lacks clarity for agents.generate_test_data— Parameter requirements for schema inputs are not explicitly defined.generate_from_template— Overlap with 'generate_test_data' may create ambiguity in tool selection.
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — era changed from unspecified to auth-gated · transition phase initiated, compliance metrics unavailable
- 2026-09-11T05:44:28.819Z — era reverted to legacy, complianceScore rose from null to 100 · stable legacy configuration achieved with full compliance
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 494ms → warm 490ms (penalty 4ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 0.2.0
- Supported versions: — → 2025-11-25
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/mockhero-mockhero)<a href="https://mcpmetrics.io/servers/mockhero-mockhero"><img src="https://mcpmetrics.io/badge/mockhero/mockhero/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see