io.github.vola-trebla/zod-contract-mock-forge-mcp
NPM · ZOD-CONTRACT-MOCK-FORGE-MCP
MCP server for deterministic mock generation and API contract scaffolding using Zod schemas
Available components
Last scanned (1 hour ago)
Scores higher than 66% of npm servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @faker-js/faker 9.9.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 100 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 169 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 960 tokens (~96/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 0
- Stability: pass → 0.97 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 0
- CVE-2023-54404 affects this package: high ▼ security
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/zod-contract-mock-forge-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-qxc2-j82w-r537 | CVE-2026-73231 | high | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 100 packages
| Packages resolved | 100 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
detect_schema_drift ~165
Compare a Zod schema in a TypeScript file against an OpenAPI spec — finds silent divergence. Use when Zod and OpenAPI docs are maintained separately and may have drifted apart. Reports missing fields, extra fields, type conflicts, and required/optional mismatches.
| Name | Type | Req | Description |
|---|---|---|---|
| openapi_file_path | string | yes | Absolute path to the OpenAPI spec (.yaml, .yml, or .json) |
| openapi_schema_name | string | – | Schema name in components.schemas to compare against. Defaults to schema_export_name. |
| schema_export_name | string | yes | Name of the exported Zod schema variable (e.g. "UserSchema") |
| zod_file_path | string | yes | Absolute path to the .ts or .js file containing the Zod schema |
No output schema declared.
No examples provided.
evaluate_schema_evolution ~138
Detect breaking changes when a Zod schema is tightened — before tests run. Generates mocks from the old schema, validates them against the new schema, and reports exactly which fields and constraints now reject previously valid data. Use when you changed a schema and want to know if existing test fixtures will break.
| Name | Type | Req | Description |
|---|---|---|---|
| old_schema_content | string | – | Full content of the old schema file. Omit to automatically retrieve the last committed version via git show HEAD. |
| schema_export_name | string | yes | Name of the exported Zod schema variable |
| schema_file_path | string | yes | Absolute path to the TypeScript file containing the updated Zod schema |
No output schema declared.
No examples provided.
generate_boundary_violations ~53
Generate intentionally invalid payloads based on a Zod schema — for negative testing. Use to answer: what invalid inputs should I test against this API?
| Name | Type | Req | Description |
|---|---|---|---|
| schema_code | string | yes | Zod schema code |
No output schema declared.
No examples provided.
generate_exhaustive_union_violations ~80
Generate violation payloads for every branch of a z.union() or z.discriminatedUnion() schema. Use when generate_boundary_violations only covers one union variant and you need full branch coverage.
| Name | Type | Req | Description |
|---|---|---|---|
| schema_code | string | yes | Zod schema code — must evaluate to a z.union() or z.discriminatedUnion() |
No output schema declared.
No examples provided.
generate_mock_variants ~112
Generate N structurally valid but value-diverse mocks from a Zod schema — for property-based testing. Use when generate_valid_mock is too deterministic and you need varied inputs to surface edge cases. Supply seed for reproducible output in CI.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Number of mock variants to generate (default: 5, max: 50) |
| schema_code | string | yes | Zod schema code |
| seed | integer | – | Seed for reproducible output — omit for random variants each call |
No output schema declared.
No examples provided.
generate_valid_mock ~64
Generate valid mock data from a Zod schema string. Use to answer: what does a valid payload for this schema look like?
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Number of mocks to generate (default: 1) |
| schema_code | string | yes | Zod schema code |
No output schema declared.
No examples provided.
introspect_schema ~63
Convert a Zod schema string to JSON Schema for LLM understanding. Use to answer: what is the structure and constraints of this schema?
| Name | Type | Req | Description |
|---|---|---|---|
| schema_code | string | yes | Zod schema code (e.g., 'z.object({ name: z.string() })') |
No output schema declared.
No examples provided.
read_schema_from_file ~85
Read a Zod schema directly from a TypeScript or JavaScript file. Use to answer: what schema is defined in this file?
| Name | Type | Req | Description |
|---|---|---|---|
| export_name | string | – | Name of the exported schema variable. If omitted, extracts the first Zod expression found. |
| file_path | string | yes | Absolute path to the .ts or .js file containing the Zod schema |
No output schema declared.
No examples provided.
scaffold_api_contract_test ~132
Generate an API contract test or mock boilerplate for Playwright, Jest, Vitest, or MSW. Use to answer: how do I write a test that validates this API endpoint against this schema?
| Name | Type | Req | Description |
|---|---|---|---|
| base_url | string | – | Base URL of the API |
| endpoint | string | yes | API endpoint path (e.g., /api/users) |
| framework | string | – | Testing framework to generate code for |
| method | string | – | HTTP method |
| schema_code | string | yes | Zod schema code for the response body |
| test_name | string | – | Name of the generated test |
No output schema declared.
No examples provided.
suggest_contract_fix ~68
Validate a JSON payload against a Zod schema and suggest fixes for each violation. Use to answer: why does this payload fail validation, and how do I fix it?
| Name | Type | Req | Description |
|---|---|---|---|
| payload | string | yes | JSON string of the failing payload |
| schema_code | string | yes | Zod schema code |
No output schema declared.
No examples provided.
How do I install the io.github.vola-trebla/zod-contract-mock-forge-mcp server?
io.github.vola-trebla/zod-contract-mock-forge-mcp runs locally as an npm package, launched with npx -y zod-contract-mock-forge-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · zod-contract-mock-forge-mcp
claude mcp add vola-trebla-zod-contract-mock-forge-mcp -- npx -y zod-contract-mock-forge-mcp
What is the io.github.vola-trebla/zod-contract-mock-forge-mcp server?
io.github.vola-trebla/zod-contract-mock-forge-mcp is listed in the public MCP registry as io.github.vola-trebla/zod-contract-mock-forge-mcp. MCP server for deterministic mock generation and API contract scaffolding using Zod schemas. This page covers its npm package (zod-contract-mock-forge-mcp).
Is the io.github.vola-trebla/zod-contract-mock-forge-mcp server safe to use?
io.github.vola-trebla/zod-contract-mock-forge-mcp scores 80 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.vola-trebla/zod-contract-mock-forge-mcp server expose?
io.github.vola-trebla/zod-contract-mock-forge-mcp exposes 10 tools: introspect_schema, read_schema_from_file, generate_valid_mock, generate_boundary_violations, generate_exhaustive_union_violations, and 5 more. Their descriptions and schemas cost roughly 960 tokens of context every time the server is loaded.
Is the io.github.vola-trebla/zod-contract-mock-forge-mcp server still maintained?
io.github.vola-trebla/zod-contract-mock-forge-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.vola-trebla/zod-contract-mock-forge-mcp server under?
io.github.vola-trebla/zod-contract-mock-forge-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.