Schema Sieve MCP server
Local JSON Schema structure inspection and privacy-safe fixture planning. Tools include inspect...
0 stars
Reviews
Write oneNobody has reviewed Schema Sieve yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Schema Sieve tools (2, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
inspect_schemaSummarize a local JSON Schema's types, properties, required fields, composition, and constraints without returning examples or defaults.
plan_fixturewrite actionCreate a privacy-safe placeholder plan for test fixture fields in a local JSON Schema. It does not fabricate or copy example data.
Public scan report
scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it
- Code scan8 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 85 days ago12/15
- Maintainer identityregistry namespace matches repository owner6/10
How Schema Sieve compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 85/100
- higher than 70% of 48,255 servers
- Tools
- 2
- the typical server has 7
- Tools that change things
- 50%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 1 read · 1 change
Install Schema Sieve in Claude Code, Cursor or VS Code
Runs npx -y schema-sieve-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add schema-sieve-mcp -- npx -y schema-sieve-mcp
What the publisher says
From the Schema Sieve repository's README, as published. We do not edit it. Read it on GitHub
schema-sieve-mcp
Schema Sieve is a local MCP tool for understanding JSON Schema files while planning tests. It focuses on the part that usually takes the most time: finding required paths, nested constraints, unions, arrays, and likely sensitive fields before writing fixtures.
Tools
- inspect_schema: summarize types, properties, required fields, constraints, composition, and references.
- plan_fixture: produce placeholder paths such as , , and without inventing or copying test data.
Safety
- Only local JSON files are accepted.
- Paths are bounded by SCHEMASIEVEROOT, which defaults to the workspace parent when launched from the package.
- Files are capped at 2 MB and results are bounded.
- Examples, defaults, constants, and sensitive-like property names are omitted or marked as omitted.
- This is structural guidance, not a JSON Schema validator and not a security scanner.
Run
npm install
npm run build
node dist/index.jsNothing above is checked by us. What we check is on the safety report.
Schema Sieve: common questions
- Is Schema Sieve MCP server safe?
- Yes, by our scan: it is graded A (85/100). Read the Schema Sieve safety report
- How do I install Schema Sieve?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Schema Sieve need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Schema Sieve maintained?
- The last commit was 87 days ago (2026-08-09). The latest release is v1.0.0.
- How does Schema Sieve compare with other MCP servers?
- safety score 85/100 (higher than 70% of 48,255 servers); tools 2 (the typical server has 7); tools that change things 50% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.