Free fit check · no source upload or payment
Describe the
boundary that matters.
Share repository and runtime metadata, not credentials or private source. The goal is to decide whether ten bounded checks can answer your next deployment decision.
The paid review, if it fits
- One rights-cleared repository revision.
- One MCP server with up to eight tools and resources.
- One disposable environment and ten agreed checks.
- Authority map, sanitized protocol packet, and failure ledger.
- One go/no-go report and one factual correction pass.
Check the server
Review first: nothing is sent while you fill in the form or choose “Review request.” Do not include source code, credentials, tokens, private data, production endpoints, exploit details, or confidential logs.
Review before sending
Check the exact request below. Nothing has been sent.
Choose how to continue. “Send fit check” encrypts the reviewed request for private review. You can also prepare it in your email app or copy it.
Before any paid review
The exact ten checks are written down.
If the server fits, the accepted scope names the revision, surface, environment, protocol cases, network boundary, handling rules, delivery, timing, and refund allocation. Direct-site clients receive a Stripe request; marketplace clients keep the contract and payment on that marketplace.