Tools · Repository Builder

MSP-1 Repository Declaration Builder

Create a root-level msp.json declaration for a GitHub repository. The declaration gives AI agents semantic context at the repository ingestion point before they inspect the repository's files, documentation, code, datasets, or other artifacts. High-value identity, canonical, provenance, trust, authority, and revision signals can travel with the repository in one declaration.

MSP-1 Aligned · 1.0.2 GitHub Repository Workflow Runs entirely in your browser — nothing you enter leaves this page

1 · Repository
2 · Meaning
3 · Trust & provenance
4 · Review & output

Repository identity

Identify the GitHub repository the declaration will travel with. The repository URL is used as both the MSP-1 site.id and site.url.

GitHub repository URL required Example: https://github.com/MSP-1-Protocol/training-datasets

Enter a GitHub repository URL in the form https://github.com/owner/repository

Repository name required Human-readable project or repository name.

Repository name is required.

Declaration status Initial declaration The first repository-root MSP-1 declaration. Revision starts at repo-rev-1 / 1.0.0. Updating an existing declaration Amends a published repository declaration. Supply the next revision number and revision version.

Meaning

Provide the semantic context that helps an agent understand the repository before deeper inspection. Keep declarations factual, concise, and useful.

Repository description One or two factual sentences describing what the repository contains or represents.

Repository intent Why the repository exists.

Interpretive frame Optional. Clarify how the repository should be understood when that context is not fully obvious from the artifacts alone.

Frame category

Trust & provenance

Add useful provenance, trust, and responsibility signals without overstating them. Deterministic repository signals such as canonical URL, provenance source, and declaration timestamp are emitted automatically.

Repository declaration

Provenance type

Provenance confidence

Provenance notes Optional. Describe relevant creation or lineage context. The repository URL and declaration timestamp are emitted automatically as provenance source and timestamp.

Trust level Defaults to medium. Raise only when the declaration supports the stronger claim.

Verification level The builder cannot independently verify a publisher, so it emits self-declared.

Revision notes Optional. Leave blank for the standard initial or update note.

Add authority Use when a real person, organization, or system has responsibility within the declared repository scope.

Authority name required if enabled

Authority type required if enabled

Authority ID or URL Optional stable identifier.

Add reviewer Only if the declaration was actually reviewed.

Reviewer name required if enabled

Reviewer type required if enabled

Role Optional.

Review & output

Review the semantic fields before publishing. The generated file uses standard MSP-1 syntax and is deployed at the repository root.

Repository declaration (`msp.json`)

Save as msp.json at the repository root and commit it with the repository.

Place the downloaded file at the repository root, then run it through the MSP-1 Validator as a final structural check.

Live msp.json preview

Updates as you type. Empty optional fields are omitted; absence remains a valid state in MSP-1.