mcp-directory-readinesslisted

# mcp-directory-readiness Audits an MCP server against the 9 verified Anthropic MCP Directory submission requirements (sources: claude.com/docs/connectors/building/submission + support.claude.com Software Directory Policy article; corrected 2026-06-02). Produces a gap list, mechanical auto-fixes where possible, and a pre-filled submission form. ## When to use - "Submit to Anthropic Directory" / "MCP submission" - "Audit my MCP server" / "Is my MCP ready for the directory" - "Directory submission checklist" - Before pasting a connector into https://clau.de/mcp-directory-submission ## Workflow ### 1. Locate the server source If not in the current working directory, ask once: "What's the path to the MCP server repo?" Default to cwd if user confirms. Identify: - Transport: remote streamable-HTTP vs local stdio (determines privacy-policy requirement) - Tool registration file (typically `server.ts`, `index.ts`, `tools/index.ts`, or wherever `tools/list` is handled) ### 2. Run the audit Walk the 9 requirements in `requirements.md`. For each, run the corresponding check from `audit-checklist.md`. The highest-leverage checks (in order): 1. **Tool annotations** — every tool needs `title` AND one of `readOnlyHint|destructiveHint`. ~30% of rejections. 2. **manifest.json present at v0.2+** with `privacy_policies` array. Newly required as of 2026 — pre-2026 skill versions missed this. 3. **No stub tools** — README must not advertise "v0.X scaffold, N tools stubbed." Reviewers smoke