MSP-1 Validator

Planned Capabilities

The MSP-1 validator is designed to work at two levels:

• Site-Level Validation
  Fetch /.well-known/msp.json and validate it against https://msp-1.com/schema/msp-1-site.json.
• Page-Level Validation
  Discover or accept a page-level descriptor and validate it against https://msp-1.com/schema/msp-1-page.json.

Planned checks include:

• Confirming the protocol and version fields are present and valid.
• Validating the site, compliance, policies, contact, and resources structure in the site declaration.
• Validating page identity fields such as page.id, page.url, and page.title.
• Checking semantic fields including topics, audience, importance, and relationships.
• Verifying date formats for created, updated, and optional reviewDue.
• Returning a structured report suitable for both humans and AI agents.

Intended Usage

The validator is intended for:

• Site owners implementing MSP-1 for the first time.
• AI agents that want to assess MSP-1 conformance for a given domain or URL.
• Tools and crawlers that integrate MSP-1 checks into their pipelines.

Example (Planned API Sketch)

The following is an illustrative example of how a future HTTP endpoint might be used. It is not yet active.

GET https://msp-1.com/validator/api?mode=site&url=https://example.com

The mode parameter could specify site (for /.well-known/msp.json) or page (for a specific page descriptor). A successful response would return a JSON object with fields such as:

• valid — overall boolean validation result
• errors — list of schema validation errors, if any
• warnings — non-fatal issues or recommendations
• siteValidation — detailed site-level results (when mode=site)
• pageValidation — detailed page-level results (when mode=page)

This structure is intended to be easy to consume by both human operators and automated systems.