Preflight

Know if your MCP server is ready to publish — before you submit.

What Preflight checks

• server.json schema compliance and required fields
• smithery.yaml presence and structure
• Registry slug format (npm MCP registry, Smithery, agenticmarket)
• Version string format and semver compliance
• Homepage URL presence and reachability flag
• remotes block structure and endpoint format
• package.json fields required for npm publish

Who it's for

Solo MCP builders and small automation agencies preparing a first or updated listing on the npm MCP registry, Smithery, or agenticmarket. If you've ever had a submission rejected for a metadata gap you didn't know was there, Preflight flags it before you submit.

How to try it

Preflight is an MCP tool. Connect your MCP client to the endpoint below and call check_publish_readiness with your server artifacts:

MCP endpoint: https://skillfoundry.synaplex.ai/products/preflight/mcp/

Tool: check_publish_readiness
Parameters:
  manifest      — contents of your server.json
  package_json  — contents of your package.json (optional)
  smithery_yaml — contents of your smithery.yaml (optional)

Or use the REST API directly:

curl -X POST https://skillfoundry.synaplex.ai/products/preflight/api/check \
  -H "Content-Type: application/json" \
  -d '{"manifest": "{...your server.json contents...}"}'

What the verdict means

checks_pass — your server meets all registry requirements audited. Ready to submit.

fixable — specific gaps found. Preflight returns each failing rule and what to change.

The signal it produces

Every check run against live registry rules. When you fix what Preflight flags, your listing passes review. Preflight is updated as registry requirements change.