Ship Your MCP Server

The preflight that blocks your MCP server before the public registry does.

R$ 79,00 — v1.0.0

12 checks: license, README, .env out of git, secrets, stdio handshake
Manifest consistency (server.json x smithery.yaml) and version
Fails with named blockers, not with a generic warning

You get 8 files (19 KB) in ship-your-mcp-server-1.0.0.zip — SKILL.md with the walkthrough plus the scripts.
sha256 98d13c948d34047f…

Stripe paymentInstant download7-day refundNo subscription

Want me to install it in your project?

Guided setup from R$ 1.500,00: I install it, wire the guards and run the first cycle with you.

See the service

How to start

Repo hygiene and manifestsThe first level does not need the server running — it reads files only.python scripts/mcp_release_preflight.py /path/to/your-mcp
Add the real stdio handshakeThis is where most servers break: the actual handshake, not the manifest.python scripts/mcp_release_preflight.py /path/to/repo --cmd "python -m my_server"
Or over streamable HTTPThe same gate against a server that is already up — the path the remote client uses.python scripts/mcp_release_preflight.py /path/to/repo --url http://127.0.0.1:8080/mcp
In CI, one lineExit code 0 only when no check FAILS; a deliberately accepted check can be downgraded — it stays in the report, never silent.python scripts/mcp_release_preflight.py . --cmd "python -m my_server" --json > preflight.json

When you will use it

Before you submit to the registry12 checks with a named blocker, not a generic warning. Exit code 0 only when no check FAILs — it can be a single CI line.
The server prints to stdout and breaks JSON-RPCThe stdio rule that sinks almost every server on its first submission, verified against the real handshake.
Manifest out of syncserver.json, smithery.yaml and the package version disagreeing is an instant rejection — the skill compares all three.
A key leaking in the repo.env tracked in git, a secret in the code and a missing SECURITY.md block the submission before the registry finds them.
Handshake before publishingBoots the server for real (stdio or streamable HTTP) and speaks MCP to it before someone else does that for you in public.

What comes in the package

scripts/mcp_release_preflight.py — the whole gate — pure stdlib, network only against your own server
references/registry-listings.md — what each registry ingests and what it rejects
references/oauth-and-auth.md — the remote server's auth path, failure by failure
templates/server.json — registry manifest in the right shape
templates/smithery.yaml — Smithery manifest in the right shape
templates/SECURITY.md — the security policy registries look for

Requirements

Python 3.8+ (stdlib only)
the MCP server repository
optional: --cmd or --url for the real handshake

Where it does not fit: It does not register anything for you — it tells you whether you pass. A check you accept on purpose can be downgraded with --allow, and the report records the downgrade (never silently).

How do I get it after paying?

The download link shows up on the thank-you page as soon as Stripe confirms, and also goes to your e-mail. If you lose it, request a resend from the same e-mail used to buy.

Can I use it on a client project?

Yes — the license covers personal and commercial use in your projects, including client work. What you cannot do is resell the package. Full terms.

Prices in Brazilian real (BRL). Stripe charges in BRL.

← all skills

Payment processed by Stripe — no card data touches this server. Instant delivery once confirmed. Prices in BRL (Brazilian real) — you are charged in BRL. Terms, delivery and refund.