Directory submission checklists
What each connector directory asks for — Anthropic's Claude connectors directory, OpenAI's ChatGPT apps and GPT Store, n8n verified nodes, Zapier — and how Aceversity meets it.
Directory requirements change; always read the current policy linked from each platform before submitting. The items below are what reviewers consistently check, mapped to where Aceversity already covers them.
Claude connectors directory (Anthropic)
| Requirement | Aceversity |
|---|---|
| Remote MCP server over HTTPS, Streamable HTTP | https://api.aceversity.com/mcp ✓ |
| OAuth 2.x with discovery (protected-resource + auth-server metadata), PKCE, dynamic client registration | ✓ (Authentication) |
Claude's OAuth callbacks accepted (https://claude.ai/api/mcp/auth_callback, https://claude.com/api/mcp/auth_callback) |
✓ any HTTPS callback is accepted via DCR; shown as Claude (verified) on the consent screen |
Every tool has a clear name, title and description; accurate readOnlyHint / destructiveHint |
✓ enforced by unit tests |
| Tools do what they say, nothing more; no prompt-like instructions to the model hidden in descriptions | ✓ |
| Reasonable tool result sizes | Lists capped at 100 items; syllabus text only on request |
| Privacy policy, support contact, documentation | aceversity.com/privacy · support@aceversity.com · this site |
| Working test account for reviewers, with sample data | Member A from Testing |
| Reliable uptime and errors that explain themselves | /health, consistent errors with request_id |
Prepare: connector name Aceversity, a one-line description ("Your syllabus-based study plan: deadlines, grades, weak topics and flashcards"), logo (square SVG/PNG), 3–5 example prompts from Claude, the server URL, reviewer credentials (create a password for the test account so reviewers don't need the emailed code), and the testing sign-off.
ChatGPT apps (MCP) and Custom GPTs
Apps / connectors (MCP): submitted from OpenAI's platform dashboard. Expect to provide: verified organization, app name/description/icon, MCP URL, OAuth working with ChatGPT's callback, privacy policy and terms, support contact, test credentials and example prompts, accurate read-only/destructive annotations (ChatGPT uses them for confirmations).
Custom GPT in the GPT Store:
- Builder profile verified with the aceversity.com domain (DNS TXT record) so the GPT shows the brand.
- Action imported from
https://api.aceversity.com/openapi.json; OAuth configured with a client registered for the GPT's callback (ChatGPT). - Privacy policy URL set on the action.
- Write operations marked consequential (done in
openapi.json). - Description and conversation starters; no claims about other students' data.
n8n verified community node
- Package
n8n-nodes-aceversity, keywordn8n-community-node-package, MIT license, built from the n8n node starter. - No runtime dependencies; credentials with a test request (
GET /v1/me). - Passes
npm run lintandnpx @n8n/scan-community-package n8n-nodes-aceversity. - Published to npm from GitHub Actions with provenance.
- README with operations list, credential setup and an example; icon in SVG.
- Submitted through the n8n Creator Portal for verification.
Zapier public integration
- OAuth v2 auth with refresh, test call
GET /v1/me, connection label from the email. - At least one trigger (new deadline — polling
created_after) and a few actions (create deadline, record grade, create flashcard deck). - Sample data for each trigger, help links to this site, an app logo, and a test account for Zapier's review.
Before every submission
- Production passes the sign-off checklist.
- Changelog updated;
info.versionbumped if the surface changed. - Reviewer test account has fresh, realistic data and an active membership that won't lapse during review.