check_publish_readiness — Preflight MCP Tool Read-only
check_publish_readiness
(check publish readiness) is one of 1 tool on the
Preflight
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_publish_readiness from your client
- Claude Code Preflight check_publish_readiness run in your project directory
- Claude Desktop Preflight check_publish_readiness ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Preflight check_publish_readiness ~/.cursor/mcp.json
- VS Code Preflight check_publish_readiness .vscode/mcp.json
- Zed Preflight check_publish_readiness ~/.config/zed/settings.json
- Windsurf Preflight check_publish_readiness ~/.codeium/windsurf/mcp_config.json
- Cline Preflight check_publish_readiness ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Preflight check_publish_readiness ~/.gemini/settings.json
- Grok Preflight check_publish_readiness .mcp.json (in your project root)
- ChatGPT Preflight check_publish_readiness Settings → Connectors → Advanced → Developer mode
- Claude.ai Preflight check_publish_readiness Settings → Connectors → Add custom connector
- LangChain Preflight check_publish_readiness pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http preflight https://skillfoundry.synaplex.ai/products/preflight/mcp/
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.