01 / capability
Canonical capability manifests
Exposed as a scoped capability with its own evidence trail, not a hidden setting.
Agents, MCP & capabilities · Concept
Ship the capability, not the glue.
A trusted machine-readable registry for discovering, validating and managing interoperable AI plugins, skills, tools and agent capabilities.
01
What it is
PluginRegistry is built for Developers, enterprises, platform providers, software publishers.
The problem
PluginRegistry replaces unverified plugin directories, fragmented registries and manually maintained integration catalogs.
The approach
A trusted machine-readable registry for discovering, validating and managing interoperable AI plugins, skills, tools and agent capabilities.
The boundary
Work stays inside an explicit scope: named sources, defined permissions, bounded execution, retained evidence.
02
Capabilities
Five contracts the product is specified around. Each one is a boundary as much as a feature.
02 / capability
Identity and provenance verification
Exposed as a scoped capability with its own evidence trail, not a hidden setting.
03 / capability
Compatibility and conformance testing
Exposed as a scoped capability with its own evidence trail, not a hidden setting.
04 / capability
Searchable registry APIs
Exposed as a scoped capability with its own evidence trail, not a hidden setting.
05 / capability
Versioning, revocation and lifecycle governance
Defined as an explicit contract so operators can review it before it runs.
03
How it works
The same three steps apply whether a person or an agent is driving.
01
Define the scope
Start from the boundary PluginRegistry is allowed to act inside: the workspace, the sources, the budget, the authority.
02
Connect the surfaces
Expose the same capability through the interface a human uses and the interface an agent calls, with one permission model.
03
Act with evidence
Every action leaves a record that can be inspected, replayed and challenged before the next one runs.
Read the specification before you believe the category.
PluginRegistry is documented as a concept: requirements, interfaces and evidence expectations. It is not presented as a live service.