io.github.vola-trebla/zod-contract-mock-forge-mcp
NPM · ZOD-CONTRACT-MOCK-FORGE-MCP · SCANNED AUG 3
MCP server for deterministic mock generation and API contract scaffolding using Zod schemas
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (102 of 106), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (102 of 106), so this covers what we could see, not the whole tree. 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 75 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · zod-contract-mock-forge-mcp
claude mcp add vola-trebla-zod-contract-mock-forge-mcp -- npx -y zod-contract-mock-forge-mcp
codex mcp add vola-trebla-zod-contract-mock-forge-mcp -- npx -y zod-contract-mock-forge-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vola-trebla-zod-contract-mock-forge-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"zod-contract-mock-forge-mcp"
],
"enabled": true
}
}
} openclaw mcp add vola-trebla-zod-contract-mock-forge-mcp --command npx --arg -y --arg zod-contract-mock-forge-mcp
mcp_servers:
vola-trebla-zod-contract-mock-forge-mcp:
command: "npx"
args: ["-y", "zod-contract-mock-forge-mcp"] {
"mcpServers": {
"vola-trebla-zod-contract-mock-forge-mcp": {
"command": "npx",
"args": [
"-y",
"zod-contract-mock-forge-mcp"
]
}
}
} 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.
- 2 Aug 26 +40
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Licence: MIT functional
- 1 Aug 26 +19
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Dependency health: partial → unverified ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 31 Jul 26 −39
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 46
First indexed and scored.
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 102 packages
102 packages in the resolved dependency tree · 99 deprecated · 32 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.