registry/internal/validators/schemas
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Wolfe-James 69374b08de
docs: add cargo and crates.io to schema examples (#1511)
The cargo registry type has been live since v1.8.0 (#1207).
This PR only updates the schema examples so they match reality.

- Add "cargo" to registryType.examples
- Add "https://crates.io" to registryBaseUrl.examples

No behaviour change.

Note: versioned schemas are synced from modelcontextprotocol/static.
A follow-up there keeps this durable across schema sync.

Co-authored-by: Wolfe-Jam <wolfejam77@gmail.com>
2026-08-10 15:19:06 +03:00
..
2025-07-09.json Enhanced server.json validation (phase 1) (#636) 2026-01-16 00:49:39 +02:00
2025-09-16.json Enhanced server.json validation (phase 1) (#636) 2026-01-16 00:49:39 +02:00
2025-09-29.json Enhanced server.json validation (phase 1) (#636) 2026-01-16 00:49:39 +02:00
2025-10-11.json Enhanced server.json validation (phase 1) (#636) 2026-01-16 00:49:39 +02:00
2025-10-17.json Enhanced server.json validation (phase 1) (#636) 2026-01-16 00:49:39 +02:00
2025-12-11.json docs: add cargo and crates.io to schema examples (#1511) 2026-08-10 15:19:06 +03:00
README.md Enhanced server.json validation (phase 1) (#636) 2026-01-16 00:49:39 +02:00

Schema Files

This directory contains JSON Schema files that are embedded into the Go binary (using the go:embed directive) for runtime validation.

How Schema Files Get Here

Schema files are automatically synced from the modelcontextprotocol/static repository via the GitHub Actions workflow .github/workflows/sync-schema.yml.

The workflow:

  1. Checks out the modelcontextprotocol/static repository
  2. Copies all versioned schema files from static-repo/schemas/*/server.schema.json
  3. Saves them here as {version}.json (e.g., 2025-10-17.json)
  4. Automatically commits and pushes any new or updated schemas

Do not manually edit files in this directory - they are managed by the sync workflow.

Usage

These schema files are embedded into the Go binary using the go:embed directive for offline schema validation. The embedded schemas are used by the validation code in internal/validators/schema.go to validate server.json files against their specified schema version.

File Naming

Files are named {YYYY-MM-DD}.json where the date corresponds to the schema version (e.g., 2025-10-17.json). This matches the version in the schema's $id field.