Developer ecosystem

CAIN Developer Marketplace

Extensions for the Trust Fabric: MCP integrations, framework adapters, policies, connectors, ActionProof modules, security rules and more. Discovered, verified, then installed.

Last reviewed

Extensions are third-party code and configuration. Every listing shows its permissions, whether the release is signed, and the security screen. CAIN does not sandbox extension code — an adapter you install runs with your process’s privileges. What the CLI checks before it installs anything →

Loading…

Browse by type

MCP integrationsWrap or proxy an MCP server.Framework adaptersLangChain, LangGraph, CrewAI and friends.PoliciesRego and declarative rules. Data, not code.ConnectorsTalk to an external system.ToolsCallables an agent can invoke.ActionProof modulesConstraints for plan verification.Security rulesetsInjection patterns and blocklists.Evidence integrationsShip decisions to a SIEM.Deployment pluginsExtend how MCPGate is deployed.SDK extensionsAdd surface to the SDKs.Enterprise integrationsSSO, RBAC, ticketing.

Install an extension

cain marketplace search redis
cain marketplace inspect acme/redis-connector   # permissions, signature, scan
cain marketplace install acme/redis-connector

Install refuses outright on a malformed manifest, an incompatible extension, a forbidden scope or a yanked version — no flag overrides those. An unverified signature needs --allow-unsigned, and that waiver is recorded in your cain-extensions.lock so an audit can find it later.

Publish an extension

cain marketplace init --type policy
# edit cain-extension.yaml -- ask for the fewest scopes you need
cain marketplace publish --dry-run     # validate, publish nothing
cain marketplace publish --signature "$SIG" --artifact-sha256 "$SHA"

Claim a publisher handle first and register a signing key. Unsigned releases can be published, but every installer has to pass a flag and carry the waiver in their lockfile — so signing is how you get adopted.

Versions are immutable. Republishing one returns a conflict; publish a new version instead. A mutable version is a supply-chain attack with extra steps: anyone who reviewed it yesterday has no way to know it changed today.

Revenue

Free and paid listings are both supported. The platform share is 20%; publishers keep 80%.

Checking payout status…