Track your directory submission changeddirectory/submission-status
Nearest release: v2.1.283, published under an hour after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 25 Sep 2026 18:00 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 22 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+10added
Lines−10removed
From line
8
where the diff opens
First seen
25 Sep 2026
this site's first read of the page
Recorded edits4to this page, all time
The whole hunk
from line 8, old and new numbered
/
from line 8
88
99> [!NOTE]
1010>
11> If you haven't submitted yet, see [Publish to the directory](/docs/directory/publish).
11> If you haven't submitted yet, see [Publish to the directory](/docs/directory/publish.md).
1212
1313Find your status in the table for your submission's kind: [plugin bundle](#plugin-bundle-statuses) or [MCP connector](#mcp-connector-statuses). If nothing is waiting on you and you still need an answer, see [Contact Anthropic about a submission](#contact-anthropic-about-a-submission).
1414
from line 20
2020| :- | :- | :- |
2121| **Draft** | Nothing has been sent to Anthropic yet | You. Select **Continue submission**. |
2222| **Scanning** | You submitted, and the security scan is waiting to start or running. If a scan attempt fails on Anthropic's side or GitHub's, the directory retries it. | Anthropic. There's nothing to do on your side. |
23| **Needs changes** | The newest version didn't pass, or the scanner couldn't fetch or accept the plugin. The plugin's page names what to change. | You. [Fix a failed version](/docs/plugins/submit#fix-a-failed-version) covers pushing a fix and resubmitting. |
23| **Needs changes** | The newest version didn't pass, or the scanner couldn't fetch or accept the plugin. The plugin's page names what to change. | You. [Fix a failed version](/docs/plugins/submit.md#fix-a-failed-version) covers pushing a fix and resubmitting. |
2424| **In review** | An Anthropic reviewer is checking the listing. When the version was held, the card names the category it's held for. The reviewer's decision appears on the plugin's page. | Anthropic |
25| **Approved** | The version passed, and it isn't live yet. The card says who publishes it: an Anthropic reviewer, you, or the directory by itself. | Whoever the card names. [Publish a passing version](/docs/plugins/submit#publish-a-passing-version) explains the publish settings. |
25| **Approved** | The version passed, and it isn't live yet. The card says who publishes it: an Anthropic reviewer, you, or the directory by itself. | Whoever the card names. [Publish a passing version](/docs/plugins/submit.md#publish-a-passing-version) explains the publish settings. |
2626| **Published** | A version is live in the directory. The card also says what is happening with any newer version, such as being scanned, waiting with a reviewer, or not passing. A newer version that doesn't pass leaves the published one unaffected. | Nobody, unless the card names a newer version that needs changes |
2727| **Not live yet** | The submission is marked published, and nothing is listed yet. The directory team has to list it. | Anthropic |
2828| **Delisted** | The plugin isn't visible in the directory. Select **Relist plugin** to ask for it back. | You, if you want it listed again |
from line 34
3434
3535Open the connector from the developer portal's list of submissions. A card at the top of the connector's page shows the status, one sentence about it, and the next step when there is one.
3636
37A submission doesn't pass through every status in the table. Anthropic scans each connector submission automatically and, by default, lists it as a Community connector with no action from you. Some submissions also get a review from a person, and the statuses that mention a reviewer apply to those. [How Anthropic reviews directory submissions](/docs/directory/publish#prepare-for-review) describes both.
37A submission doesn't pass through every status in the table. Anthropic scans each connector submission automatically and, by default, lists it as a Community connector with no action from you. Some submissions also get a review from a person, and the statuses that mention a reviewer apply to those. [How Anthropic reviews directory submissions](/docs/directory/publish.md#prepare-for-review) describes both.
3838
3939| Status | What it means | Who acts next |
4040| :- | :- | :- |
from line 45
4545| **Approved** | The review team cleared the listing, and it isn't in the directory yet. It goes live when someone who can edit the listing publishes it. If you edit the listing before you publish, it returns to draft for another review. | You. Select **Publish**. |
4646| **Published** | The connector is live in the directory. If you submitted an edit, the card says whether that edit is in review, and the live listing stays until the edit is approved. | Nobody |
4747
48[Manage your directory listing](/docs/connectors/building/managing-your-listing) covers reviewer feedback, listing edits, and the health and usage metrics for a published connector.
48[Manage your directory listing](/docs/connectors/building/managing-your-listing.md) covers reviewer feedback, listing edits, and the health and usage metrics for a published connector.
4949
5050## Contact Anthropic about a submission
5151
from line 58
5858
5959## After your listing is published
6060
61A published listing appears in the directory that claude.ai, the Claude desktop and mobile apps, and Cowork share. [Plugin feature support across platforms](/docs/plugins/platform-support) lists which of a plugin's components load on each surface.
61A published listing appears in the directory that claude.ai, the Claude desktop and mobile apps, and Cowork share. [Plugin feature support across platforms](/docs/plugins/platform-support.md) lists which of a plugin's components load on each surface.
6262
63A published connector is listed with the **Community** label by default. There's no application for the **Verified** label. [Connector verification](/docs/connectors/verification#list-your-own-connector) explains how a listing becomes Verified and what each label means to people installing it.
63A published connector is listed with the **Community** label by default. There's no application for the **Verified** label. [Connector verification](/docs/connectors/verification.md#list-your-own-connector) explains how a listing becomes Verified and what each label means to people installing it.
6464
6565## Next steps
6666
67* [After publishing](/docs/connectors/building/after-publishing): update your server or plugin, and delist
68* [Submit your plugin](/docs/plugins/submit#after-you-submit-a-plugin): follow each new plugin version through the scan, review, and publishing
69* [Manage your directory listing](/docs/connectors/building/managing-your-listing): for a connector, read reviewer feedback, edit the listing, and check its metrics
67* [After publishing](/docs/connectors/building/after-publishing.md): update your server or plugin, and delist
68* [Submit your plugin](/docs/plugins/submit.md#after-you-submit-a-plugin): follow each new plugin version through the scan, review, and publishing
69* [Manage your directory listing](/docs/connectors/building/managing-your-listing.md): for a connector, read reviewer feedback, edit the listing, and check its metrics
7070
No line in this hunk matches that.