Skip to content
ECZ-IDPlugin
Verify an ECZ-ID

Works alongside

What an ECZ-ID Plugin Passport sits beside

A Plugin Passport works with the marketplaces and permission models your plugin already lives in. Listings stay where they are; the Passport ties them to one identity.

Adjacent systems

What each already does, and what the Passport adds

ECZ-ID complements your frameworks, protocols, OAuth, cloud IAM and workload identity. It replaces none of them and stays outside the execution path.

  • Extension and app marketplaces

    What it does
    Distribute plugins, extensions and apps, under their own review processes.
    What an ECZ-ID adds
    One identity across every store, with each listing recorded as a binding rather than a second identity.

  • Source repositories

    What it does
    Host the code a library, plugin or server is built from.
    What an ECZ-ID adds
    A binding from the repository to the enduring subject, recorded with where it was learned.

  • OAuth 2.x and OpenID Connect

    What it does
    Delegate authorisation and authenticate a principal for a session.
    What an ECZ-ID adds
    A durable public record of the subject and its operator that outlives any token and needs none to read.

  • Model Context Protocol (MCP)

    What it does
    Connects AI applications to tools and data through a defined client–server protocol.
    What an ECZ-ID adds
    A resolvable identity for the agent and, separately, for each MCP server it uses — each with a named operator.

Adjacent identities

The Passports that surround this one

Each is a separate subject with its own operator and its own identity. None is issued for you, and none is implied by holding this one.

  • ECZ-ID Agent Passport™

    Plugins extend agents. The agent a plugin serves is a separate subject with its own Passport.

  • ECZ-ID MCP Passport™

    Plugins frequently bundle or connect to MCP servers, and each server is identified in its own right.

  • ECZ-ID API Passport™

    Most plugins call an API. The API keeps one identity across every plugin that uses it.

  • ECZ-ID SDK Passport™

    Plugins are built on SDKs and published as packages, each of which can carry its own publisher identity.