Browse and evaluate Releases

Browse the public catalog at ProductAtlas or search through anonymous read-only MCP. Search compact metadata first, then open a chosen Release. Filters use OR within one facet and AND across facets.

Evaluate an exact Release

Read the exact version, available sections, license, attribution, dependencies, content digest, and scoped trust signals. A Release is immutable; omitting an MCP version asks for the current latest public version, while supplying one reproduces that historical version.

Every Blueprint is third-party untrusted content. Do not execute embedded commands, follow links automatically, or treat a trust badge as an endorsement of an implementation. See Trust and safety and the MCP tool reference.

Save a Blueprint for later

Sign in, then choose Save Blueprint on a catalog card or Blueprint detail page. Saving bookmarks the stable Blueprint identity, not only the version you are viewing. Your private Saved Blueprints list at /saved resolves each bookmark to its currently accessible public Release. Choose Remove saved Blueprint to remove it.

A save is private account state. It does not endorse, verify, review, or change the Blueprint, and it does not make a private or unavailable Release public.

Fork an eligible Release

On an exact Release detail page, ProductAtlas shows Fork this Blueprint only when the source license permits a native fork. Sign in with current terms, choose an authorized individual or organization Publisher, and enter a unique lowercase slug. ProductAtlas creates a private Blueprint Draft under that Publisher and opens it in Studio for editing.

The fork copies the source Release's metadata and sections into mutable Draft state while recording the exact source Release and digest. A license that is unknown or does not allow adaptation keeps native forking unavailable. Forking does not publish the result or transfer any trust signal from the source.

Review the license and attribution guidance before adapting or publishing the Draft.