OnlineCyberTools MCP (280+ filterable tools)

data_mock_api_generator

Read-only

Generate mock REST API endpoints by defining paths, methods, field types, and record counts. Returns fabricated records grouped by route for multi-endpoint API fixtures.

Instructions

Mock API Generator (Build Mock REST API From JSON Schema). Generate a small in-memory mock REST API document from a JSON schema template: given an array of endpoints (each a path, HTTP method, record count, and a list of typed fields), it fabricates fake records per endpoint and returns them grouped by path. Field types include uuid, integer, float, boolean, full_name, first_name, last_name, email, phone, iso_date, iso_datetime, sentence, paragraph, and enum. Use this when you need multi-endpoint API fixtures keyed by route; use data_faker for a single flat list of richly namespaced person/finance fields, data_random_data_generator for one flat record set across many primitive types with CSV/TSV/NDJSON output, or data_sample_data_generator for curated ready-made domain datasets (users, orders, logs). Output is random and non-idempotent — an optional seed makes record bodies reproducible, but the generatedAt timestamp still varies each call. Runs locally, read-only, contacts no external service, and is rate-li

Input Schema

TableJSON Schema

Name	Required	Description	Default
`template`	Yes	Schema describing the endpoints to fabricate.
`seed`	No	Optional seed; when set, record bodies are reproducible (generatedAt still varies). Omit for crypto-random output.

Output Schema

TableJSON Schema

Name	Required	Description
`success`	No	True when generation succeeded.
`info`	No	Summary of the generated document.
`endpoints`	No	One entry per requested endpoint.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed28 schema fields changedv0.5.1Jun 3, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / seed / description

Added value: +"Optional seed; when set, record bodies are reproducible (generatedAt still varies). Omit for crypto-random output."

addedInput schema / properties / seed / maxLength
```
Added value: +1024
```
addedInput schema / properties / template / additionalProperties
```
Added value: +false
```

addedInput schema / properties / template / description

Added value: +"Schema describing the endpoints to fabricate."

addedInput schema / properties / template / properties / endpoints / description

Added value: +"Endpoints to generate; total records across all endpoints must not exceed 5000."

addedInput schema / properties / template / properties / endpoints / items / additionalProperties
```
Added value: +false
```
addedInput schema / properties / template / properties / endpoints / items / properties / count / description
```
Added value: +"Number of records to generate for this endpoint."
```
addedInput schema / properties / template / properties / endpoints / items / properties / count / maximum
```
Added value: +1000
```
addedInput schema / properties / template / properties / endpoints / items / properties / count / minimum
```
Added value: +1
```
addedInput schema / properties / template / properties / endpoints / items / properties / fields / description
```
Added value: +"Field specifications for each record; field names must be unique within an endpoint."
```
addedInput schema / properties / template / properties / endpoints / items / properties / fields / items / additionalProperties
```
Added value: +false
```
addedInput schema / properties / template / properties / endpoints / items / properties / fields / items / properties / name / description
```
Added value: +"Output property name for this field."
```

added

Input schema / properties / template / properties / endpoints / items / properties / fields / items / properties / options

Added value: +{
+  "description": "Per-type options: integer/float min/max (float adds decimals 0-15), iso_date/iso_datetime from/to (yyyy-mm-dd), enum values (non-empty string array).",
+  "type": "object"
+}

addedInput schema / properties / template / properties / endpoints / items / properties / fields / items / properties / type / description
```
Added value: +"Generator type for the field value."
```

added

Input schema / properties / template / properties / endpoints / items / properties / fields / items / properties / type / enum

Added value: +[
+  "uuid",
+  "integer",
+  "float",
+  "boolean",
+  "full_name",
+  "first_name",
+  "last_name",
+  "email",
+  "phone",
+  "iso_date",
+  "iso_datetime",
+  "sentence",
+  "paragraph",
+  "enum"
+]

addedInput schema / properties / template / properties / endpoints / items / properties / fields / maxItems
```
Added value: +50
```
addedInput schema / properties / template / properties / endpoints / items / properties / fields / minItems
```
Added value: +1
```
addedInput schema / properties / template / properties / endpoints / items / properties / method / default
```
Added value: +"GET"
```
addedInput schema / properties / template / properties / endpoints / items / properties / method / description
```
Added value: +"HTTP method for the endpoint."
```
addedInput schema / properties / template / properties / endpoints / items / properties / method / enum
```
Added value: +[
+  "GET",
+  "POST",
+  "PUT",
+  "PATCH",
+  "DELETE",
+  "HEAD",
+  "OPTIONS"
+]
```
addedInput schema / properties / template / properties / endpoints / items / properties / path / description
```
Added value: +"Endpoint path, preserved verbatim (e.g. /users or /users/:id). Required, non-empty."
```
addedInput schema / properties / template / properties / endpoints / items / properties / path / examples
```
Added value: +[
+  "/users"
+]
```

changedInput schema / properties / template / properties / endpoints / items / required

Previous value: -[
-  "path",
-  "method",
-  "count",
-  "fields"
-]New value: +[
+  "path",
+  "count",
+  "fields"
+]

addedInput schema / properties / template / properties / endpoints / maxItems
```
Added value: +20
```
addedInput schema / properties / template / properties / endpoints / minItems
```
Added value: +1
```

changedInput schema / required

Previous value: -[
-  "template",
-  "seed"
-]New value: +[
+  "template"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "endpoints": {
+      "description": "One entry per requested endpoint.",
+      "items": {
+        "properties": {
+          "method": {
+            "description": "Resolved HTTP method (defaults to GET).",
+            "type": "string"
+          },
+          "path": {
+            "description": "The endpoint path, as supplied.",
+            "type": "string"
+          },
+          "records": {
+            "description": "Generated records; each is an object keyed by the requested field names.",
+            "items": {
+              "type": "object"
+            },
+            "type": "array"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "info": {
+      "description": "Summary of the generated document.",
+      "properties": {
+        "endpointCount": {
+          "description": "Number of endpoints generated.",
+          "type": "integer"
+        },
+        "generatedAt": {
+          "description": "ISO 8601 generation timestamp; varies each call even with a seed.",
+          "type": "string"
+        },
+        "totalRecords": {
+          "description": "Total records across all endpoints.",
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "success": {
+      "description": "True when generation succeeded.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 31, 2026

TDQS

A4.5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Description adds detail beyond annotations: randomness, seed reproducibility (with caveat about generatedAt), local execution, read-only nature, and rate limiting. Consistent with annotations (readOnlyHint=true, idempotentHint=false) and enriches agent understanding.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, well-organized into purpose, usage comparison, and behavioral notes. However, it is somewhat verbose and includes redundant information (e.g., field types already in schema). Minor truncation at end does not impair clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, usage, input structure, field types, behavioral traits, and alternatives. Output format is mentioned as 'grouped by path' and output schema provides complete structure. Truncation of final sentence ('rate-li') slightly reduces completeness but core information is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% description coverage, so the description adds little new parameter information. It summarizes field types and endpoint structure, but these are already detailed in the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool generates mock REST APIs from JSON schema with multiple endpoints. It explicitly distinguishes itself from sibling tools (data_faker, data_random_data_generator, data_sample_data_generator) by naming them and describing their different use cases.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance: 'Use this when you need multi-endpoint API fixtures keyed by route' and lists three specific alternatives with concise descriptions of when to use each.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server