Reported issues for zod-contract-mock-forge-mcp

Pod holds 9 of 9 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to zod-contract-mock-forge-mcp.

Most discussed

feat: add evaluate_schema_evolution tool

Problem

When a Zod schema is tightened — new required field added, string narrowed to enum, optional made required — existing static mocks in test fixtures and DB seed files silently become invalid. These only surface as confusing runtime failures deep in the test suite, long after the schema change was merged.

What the agent gains

Pre-flight breaking change detection that runs before tests. Identifies exactly which mocks are now invalid, the precise field path, and the expected vs rece

Read the thread · 2026-05-18 · closed · 0 comments

feat: add detect_schema_drift tool (Zod vs OpenAPI)

Problem

Teams maintaining both a Zod schema (runtime validation) and an OpenAPI spec (docs / client generation) inevitably let them diverge. Zod adds a required field — OpenAPI isn't updated. Result:

AI agents reading docs hallucinate non-existent or incorrect payloads
Downstream client generation breaks silently
Integration tests pass locally but fail against the real API

This is called schema drift, and it's invisible until something breaks at runtime.

What the agent gains

Exp

Read the thread · 2026-05-18 · closed · 0 comments

feat: add generate_mock_variants tool for property-based testing

Problem

generate_valid_mock is deterministic — the same schema always produces the exact same output. This is valuable for snapshot tests, but property-based testing requires diverse valid inputs to surface edge cases that a single static payload misses.

Examples of edge cases only discoverable with varied mocks:

Empty string passing .min(1) check due to off-by-one in custom validator
Max-length strings triggering DB column overflow
Random array lengths exposing pagination bugs

Read the thread · 2026-05-18 · closed · 0 comments

feat: add generate_exhaustive_union_violations tool

Problem

generate_boundary_violations currently tests only the first or last variant of union/discriminated union schemas. A z.discriminatedUnion with 5 branches leaves 3–4 branches completely untested. Common missed violations:

Missing discriminator key
Discriminator key with wrong literal value (no branch matches)
Correct discriminator but type mismatch deep in a specific branch

What the agent gains

Total branch coverage for polymorphic schemas — every union variant gets tar

Read the thread · 2026-05-18 · closed · 0 comments

Add unit and integration tests for MCP server

Add tests for core logic like 'parseZodSchema' and integration tests for the MCP server using the SDK's testing utilities.