MPAI Store
The trusted hub for MPAI implementations
MPAI writes the standards. Developers build interchangeable AI building blocks — AI Modules and AI Workflows — to those standards. The Store registers those developers, validates what they submit, assigns identifiers, and publishes the result with a cryptographic trust handshake so consumers can verify authenticity before they download and run it.
$ STORE=https://mpai.store AIM=MMC-TIQ-V2.5 ROOT_KID=$PINNED_ROOT bash verify.sh
MPAI0042-blipvqa_linux-MMC-TIQ-V2.5 FEASIBLE score=0.903
Signature Verified Successfully
Signature Verified Successfully
ACCEPT — MPAI0042-blipvqa_linux-MMC-TIQ-V2.5 (counter-signed by the implementer)Standard tools only — curl, jq,
openssl, sha256sum. There is no Store-supplied CLI to install, and none is
needed. Get verify.sh (section D) →
Verified means authentic and unmodified, not safe: we sign metadata, not code.
How it works
Register, publish, verify
Three steps take an implementation from a developer's build to a consumer that can trust it — the same funnel the real MPAI ecosystem follows.
Apply
Apply with your organization's details. Once your application is approved you receive a
unique Implementer ID (e.g. MPAI0042) and collect a submission
token from your account.
Submit & publish
Send your AIM metadata JSON. We validate it against the MPAI schema and the AIM's own definition, assign an Implementation ID, and sign it.
Verify & consume
A consumer (the SCI) searches the registry, fetches the signed statement, and verifies the signature and hashes before installing the AIMs.
What you can rely on
Signed & verifiable
Every published implementation carries an Ed25519 trust statement (TUF-like) that a consumer verifies offline before it runs.