MockHero
Server Details
Generate realistic relational test data — 156 field types, 22 locales, JSON/CSV/SQL, free previews.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- dinosaur24/mockhero
- GitHub Stars
- 1
- Server Listing
- mockhero
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.1/5 across 9 of 9 tools scored. Lowest: 3.4/5.
Most tools have clearly distinct purposes, but `generate_from_template` and `generate_test_data` could be confused if an agent does not read descriptions carefully, as both produce test data. However, the descriptions adequately differentiate them by input type (template vs. schema/prompt).
All tool names follow a consistent `verb_noun` pattern with underscores (e.g., `create_agent_checkout`, `list_templates`). No mixing of styles, making the naming predictable.
With 9 tools, the server is well-scoped for its purpose—covering checkout, estimation, schema detection, data generation, and listing utilities. No tool feels redundant or missing.
The tool surface covers the full workflow from schema detection to data generation and payment handling. Missing features like schema update or key management are minor and do not severely impact core functionality.
Available Tools
9 toolscheck_agent_checkout_statusRead-onlyInspect
Poll a Polar checkout created by create_agent_checkout using the returned claim_token.
| Name | Required | Description | Default |
|---|---|---|---|
| token | Yes | claim_token returned by create_agent_checkout. |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
claim_agent_api_keyInspect
Claim the MockHero API key after Polar marks the loginless agent checkout as paid. The key is returned once.
| Name | Required | Description | Default |
|---|---|---|---|
| token | Yes | claim_token returned by create_agent_checkout. |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
create_agent_checkoutInspect
Create a loginless Polar Checkout URL for MockHero's metered agent plan. Polar is the Merchant of Record for checkout, tax collection, and remittance. The card payment step needs a human: present the returned url to your operator together with the estimate_agent_usage cost, keep the claim_token private, then poll check_agent_checkout_status and call claim_agent_api_key once paid.
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | Billing email for the agent or the agent operator. |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
detect_schemaRead-onlyInspect
Convert SQL CREATE TABLE statements or one sample JSON object into a MockHero schema that can be passed to generate_test_data.
| Name | Required | Description | Default |
|---|---|---|---|
| sql | No | SQL CREATE TABLE statement or statements. | |
| sample_json | No | Single example JSON object to infer fields from. |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
estimate_agent_usageInspect
Estimate MockHero agent-plan cost before generating data. No login or API key is required; include an API key only when you want the estimate to use actual daily usage.
| Name | Required | Description | Default |
|---|---|---|---|
| seed | No | Seed for reproducible output. | |
| scale | No | Multiplier for template record counts. | |
| format | No | json | |
| locale | No | Default locale such as en, de, fr, es, or ja. | |
| prompt | No | Plain-English data request. Example: 50 users and 200 orders linked to them. | |
| tables | No | ||
| api_key | No | Optional MockHero API key for no-auth MCP clients. Prefer the Authorization header when the client supports it. | |
| template | No | ||
| sql_dialect | No | ||
| daily_used_before | No | Optional assumption when no API key is supplied. | |
| estimated_records | No | Required for prompt estimates because this tool does not run prompt-to-schema conversion. |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
generate_from_templateInspect
Generate realistic test data from a pre-built MockHero template: ecommerce, blog, saas, or social. Small template previews up to 100 records can run free; larger or production usage requires a MockHero API key.
| Name | Required | Description | Default |
|---|---|---|---|
| seed | No | ||
| scale | No | ||
| format | No | json | |
| locale | No | ||
| api_key | No | Optional MockHero API key for no-auth MCP clients. Prefer the Authorization header when the client supports it. | |
| template | Yes | ||
| sql_dialect | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
generate_test_dataInspect
Generate realistic JSON, CSV, or SQL test data from structured tables or a plain-English prompt. Explicit table schemas up to 100 records can run free as a proof-of-work preview; plain-English prompt generation, larger requests, and production usage require a MockHero API key.
| Name | Required | Description | Default |
|---|---|---|---|
| seed | No | Seed for reproducible output. | |
| format | No | json | |
| locale | No | Default locale such as en, de, fr, es, or ja. | |
| prompt | No | Plain-English data request. Example: 50 users and 200 orders linked to them. | |
| tables | No | ||
| api_key | No | Optional MockHero API key for no-auth MCP clients. Prefer the Authorization header when the client supports it. | |
| sql_dialect | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
list_field_typesRead-onlyInspect
List MockHero field types, descriptions, parameters, and examples before building a schema.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
list_templatesRead-onlyInspect
List MockHero's pre-built schema templates for ecommerce, blog, SaaS, and social apps.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.