Preflight

io.github.evanfollisPublished by GitHub account evanfollisv0.1.1Updated Oct 24, 2026

Check if your MCP server is ready to publish on the MCP Registry, Smithery, or npm.

The publisher's own server: Preflight

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Preflight is a remote MCP server that checks whether an MCP server is ready to publish on the MCP Registry, Smithery, or npm.

What you can do
Validate whether an MCP server is publishable on real directories such as the MCP Registry, Smithery and npm, returning evidence-backed findings tied to source-linked directory rules.
When to use it
Use it before submitting an MCP server to the MCP Registry, Smithery or npm, to catch readiness problems and see which directory rules a package fails.
Requirements
A remote Streamable HTTP endpoint; no package, environment variables or headers are declared, and no authentication is declared.
Before you install
The tool returns raw artifact contents, so review what it reports before sharing results; no credentials, payments or write actions are shown in the input.

Installation

In SourceWeft

  1. Open Preflight in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.evanfollis%2Fpreflight/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "preflight": {
      "type": "http",
      "url": "https://skillfoundry.synaplex.ai/products/preflight/mcp/"
    }
  }
}

README

skillfoundry-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.

bash
make setupmake 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 offerings
  • docs/BUILD_NEXT_PORTFOLIO.md: current ranking of the next revenue lanes
  • docs/LEARNING_LAB.md: standard for turning launches and failures into reusable learning
  • docs/HYPOTHESIS_TEMPLATE.md: required hypothesis format for major changes
  • docs/SKILL_FACTORY_SCORECARD.md: build-next scoring heuristic
  • docs/TELEMETRY_MODEL.md: minimum telemetry and evidence envelope for compounding learning
  • docs/SKILL_PROPOSAL_TEMPLATE.md: required pre-build probe template
  • docs/PORTFOLIO_INTAKE.md: intake workflow for new product and suite ideas before they graduate into active builds
  • docs/POST_LAUNCH_REVIEW_TEMPLATE.md: required after-launch learning template
  • docs/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:

bash
corepack pnpm install

Source: README.md at commit b35b0d5

Tools

1

check_publish_readiness

Validate whether an MCP server is publishable on real directories (MCP Registry, Smithery, npm). Provide raw artifact contents. Returns evidence-backed findings with source-linked directory rules.

Parametersreadmemanifestpackage_jsonsmithery_yamlpyproject_tomltarget_directories

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Preflight integrations