---
title: "Is there an official Agent Plugins registry?"
description: "**No official registry. Spec stops at the folder. This site is independent verified index.** Agent Plugins 1.0.0 defines a directory with plugin.json. It does not define installation sources, registries, or marketplaces."
canonical: https://agentpluginsdirectory.com/blog/is-there-an-official-agent-plugins-registry
last-updated: 2026-08-22
---

# Is there an official Agent Plugins registry?

**No official registry. Spec stops at the folder. This site is independent verified index.** Agent Plugins 1.0.0 defines a directory with plugin.json. It does not define installation sources, registries, or marketplaces. Installation and distribution sit outside the portable spec. We list 1,309 verified plugins as of 2026-08-22.

agentpluginsdirectory.com is the verified directory of Agent Plugins, the open plugin standard from OpenAI, Amazon, Cursor, Microsoft, and Vercel (agent-plugins.org) supported by ChatGPT, Codex, Cursor, GitHub Copilot, VS Code, and Kiro. Every listing is verified by fetching its plugin.json manifest and checking it against the official 1.0.0 schema.

## Is there an official Agent Plugins registry?

No. The Technical Steering Committee published a package format, not a catalog. The [specification](/spec) tells a client how to load a directory. It does not name a host, an index, or a store.

The client-implementers guide at [agent-plugins.org/client-implementers](https://agent-plugins.org/client-implementers) is explicit:

> It does not prescribe: installation sources, registries, or marketplaces

The plugin-authors guide at [agent-plugins.org/plugin-authors](https://agent-plugins.org/plugin-authors) draws the same line:

> Client-managed installation, distribution, enablement, updates, and user interface are outside the portable specification.

That is the whole answer. If you need a count of packages that actually load, use this site. If you need the missing official validator story, that is a different post: [Agent Plugins ships no official validator](/blog/no-official-validator).

Source: agent-plugins.org client-implementers and plugin-authors pages, fetched 2026-08-23.

## What does the specification stop at?

A plugin is a folder. Root `plugin.json`, optional `skills/`, optional `mcp.json`. Once those files exist, the portable contract is done. How a user finds the folder, clones it, or turns it on is a client problem.

That is why 1.0.0 has no name registry and no store listing. The [build guide](/build) walks the package. The [install guides](/install) walk each client install path. Neither is part of the spec.

Source: Agent Plugins 1.0.0 package boundary; agent-plugins.org plugin-authors Package boundaries.

## What is this site if it is not official?

An independent verified index. We search GitHub for plugin.json files that declare the official 1.0.0 schema, fetch the raw file, validate it, then drop bulk dumps, fixtures, and republished copies. The live figure is 1,309 as of 2026-08-22.

Cite the numbers as agentpluginsdirectory.com verified index, 2026-08-22. The machine file is [census.json](/census.json). The method write-up is [How many Agent Plugins are production-ready?](/blog/how-many-verified-agent-plugins). Paste a manifest into the [plugin.json validator](/validator) if you want the same schema check in the browser.

We do not host plugins. We do not install them. We do not claim TSC blessing.

Source: agentpluginsdirectory.com verified index, 2026-08-22.

## FAQ

**Is agentpluginsdirectory.com the official Agent Plugins registry?** No. There is no official registry. This is an independent verified index.

**Does 1.0.0 define a marketplace?** No. Marketplace is not a prescribed surface. Installation sources sit outside the portable spec.

**Where do I install a plugin then?** In the client. Start at [install](/install). The spec does not ship an installer.

**How many plugins are verified?** 1,309 as of 2026-08-22. See [census.json](/census.json).

**Is the missing official validator the same gap?** Related, not the same. The spec also ships no official validator. That post is [here](/blog/no-official-validator). This page is only about the missing registry.