Registry · 2026-10-20

The OpenMHS registry

A static, searchable index of packages that can become OpenMHS endpoints — with their bridge family, integration tier, adoption ring, evidence state and next action. A catalogue, not a control plane.

2,967records
0manifests detected
1,918capability claims
37families

Filters

Searches names, descriptions, capabilities, interfaces and licences.

Refine

Evidence is not support. Ring and evidence describe how a record was produced, not whether the package runs or conforms.

Search results

Loading registry…

Loading 2,967 records…

    How records are made

    Catalogue fields, bounded static scanning and — for a smaller set — an agent reading the actual source. The registry preserves the difference instead of flattening it into “supported”.

    Registry specification

    Trust

    All records are currently unsigned. A trust level is displayed next to every capability; an unsigned claim must never be treated as verified. No record here is a conformance certificate.

    Trust and signing

    Use the data

    The explorer is a static projection of the same JSON Lines records. Download the registry bundle, mirror it, or query it offline. No account, no API key, no tracking.

    Registry bundle