About Preflight
Preflight is an MCP server readiness checker for developers preparing to publish to the MCP Registry, Smithery, or npm. The supplied repository README does not describe its checks or workflow.
Key features
- 01MCP server publication readiness checks
Use cases
- 01Checking a server before publishing to the MCP Registry, Smithery, or npm
MCP support
The tagline describes checking MCP server readiness for publication to registries and npm; it does not specify MCP tools or resources exposed by Preflight.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://skillfoundry.synaplex.ai/products/preflight/mcp/claude mcp add --transport http evanfollis-preflight https://skillfoundry.synaplex.ai/products/preflight/mcp/{"mcpServers":{"evanfollis-preflight":{"type":"http","url":"https://skillfoundry.synaplex.ai/products/preflight/mcp/"}}}Open in Cursor{"servers":{"evanfollis-preflight":{"type":"http","url":"https://skillfoundry.synaplex.ai/products/preflight/mcp/"}}}Open in VS Code{"mcpServers":{"evanfollis-preflight":{"type":"http","url":"https://skillfoundry.synaplex.ai/products/preflight/mcp/"}}}{"mcpServers":{"evanfollis-preflight":{"serverUrl":"https://skillfoundry.synaplex.ai/products/preflight/mcp/"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
1| Parameter | Type | Required | Description |
|---|---|---|---|
| readme | string | No | Raw README content |
| manifest | string | No | Raw server.json content |
| package_json | string | No | Raw package.json content |
| smithery_yaml | string | No | Raw smithery.yaml content |
| pyproject_toml | string | No | Raw pyproject.toml content |
| target_directories | array | No | Directories to check against. Defaults to all applicable. |
Details
From the project READMEskillfoundry-products
skillfoundry-products is the implementation repository for the probes, mechanisms,
and offerings that Skillfoundry builds and operates.
Lifecycle: active. This monorepo is the canonical source for its maintained products, including Preflight.
Verified today: TypeScript workspace checks and both Python suites run through the root gate. Registry publication is separate and occurs only from pinned, checksum-verified OIDC workflows.
make setup
make check
See docs/architecture.md for ownership boundaries, artifact roles, and dated migration exceptions.
This repo has two different lanes on purpose:
mechanisms/: internal factory tools that help Skillfoundry identify, design, and improve opportunities. These are not automatically public products.products/: external, user-facing software artifacts that have been selected for public deployment, distribution, and monetization.templates/: reusable implementation starters for future external product lanes.
Public product routing should stay platform-centric. The preferred external shape is:
https://skillfoundry.synaplex.ai/products/<product-slug>/...
not one public hostname per product.
The distinction matters. Internal mechanisms help the agent system think and decide better. External products are what we eventually sell or distribute through channels such as AgenticMarket.
Default External Stack
The default lane for new external MCP offerings or probes is now:
- TypeScript-first
- remote MCP over Streamable HTTP
- Cloudflare Workers for stateless offerings
- Skillfoundry-owned public routes for the canonical runtime surface
That keeps the runtime independent from any single marketplace while preserving a simple path to distribution through registries and marketplaces later.
Current Layout
mechanisms/bottleneck-radar/: internal MCP mechanism for turning noisy source signals into ranked bottlenecks and builder-ready opportunity briefs.products/launchpad-lint/: first external MCP product candidate for auditing launch readiness and drafting marketplace launch packages.templates/remote-skill-ts/: default starter for new remote TypeScript MCP probes or offerings.
Working Rule
Do not treat a mechanism as an offering by default.
A mechanism graduates into an offering only when Skillfoundry has made an explicit decision that:
- the user-facing utility is clear,
- the deployment surface is chosen,
- the pricing or monetization path is chosen,
- and the artifact deserves its own external lifecycle.
Factory Documents
docs/CASHFLOW_ENGINE.md: repo-level operating loop for commercial probes and offeringsdocs/BUILD_NEXT_PORTFOLIO.md: current ranking of the next revenue lanesdocs/LEARNING_LAB.md: standard for turning launches and failures into reusable learningdocs/HYPOTHESIS_TEMPLATE.md: required hypothesis format for major changesdocs/SKILL_FACTORY_SCORECARD.md: build-next scoring heuristicdocs/TELEMETRY_MODEL.md: minimum telemetry and evidence envelope for compounding learningdocs/SKILL_PROPOSAL_TEMPLATE.md: required pre-build probe templatedocs/PORTFOLIO_INTAKE.md: intake workflow for new product and suite ideas before they graduate into active buildsdocs/POST_LAUNCH_REVIEW_TEMPLATE.md: required after-launch learning templatedocs/ADVERSARIAL_REVIEW_PRIMITIVES.md: multi-lens skeptical review primitive for sharpening products and extracting reusable heuristics
TypeScript Workspace Setup
The repo now includes a pnpm workspace for future TypeScript skills. If pnpm is not
installed globally, use corepack:
corepack pnpm install
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.