{"id":"140891c8-ac0a-427e-9694-ab76f79c7edc","slug":"smithery-evan-follis-u0ll-preflight","name":"preflight","description":"Check if your MCP server is ready to publish on the MCP Registry, Smithery, or npm.\n\nPreflight validates your server's actual artifacts — `server.json`, `package.json`, `smithery.yaml` — against the documented requirements of each directory. Every finding includes the evidence found, the directory rule it maps to, and the exact fix.\n\n## What it checks\n\n- **MCP Registry** — server.json schema, name format, packages/remotes config, transport type, npm mcpName ownership, PyPI README marker\n- **Smithery** — Streamable HTTP transport, public HTTPS endpoint, server-card presence\n- **npm** — name, version, entry point (bin/main)\n\nEach finding is tagged with evidence level (`verified_from_artifact` or `inferred`), rule type (`hard_requirement`, `directory_convention`, or `heuristic`), and a source URL linking to the directory documentation.\n\n## How to use\n\nCall `check_publish_readiness` with raw artifact contents (all fields optional):\n\n- `manifest` — your server.json\n- `package_json` — your package.json\n- `smithery_yaml` — your smithery.yaml\n- `pyproject_toml` — your pyproject.toml\n- `readme` — your README\n- `target_directories` — optional array of `mcp_registry`, `smithery`, `npm`\n\nReturns a verdict (`checks_pass`, `fixable`, or `not_ready`), per-directory readiness, and evidence-backed findings with concrete fixes.\n\nZero dependencies. No LLM calls. No authentication. No PII collection.","capabilities":[],"protocols":["MCP"],"safetyScore":86,"overallRank":37.9,"trustScore":null,"trust":null,"source":"SMITHERY","updatedAt":"2026-05-16T06:10:10.255Z"}