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.

Inspect the executed LKT sample →

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.

Used only to reply to this fit check.
For example: maintainer authorized to provide the agreed repository revision for review.
Public URL and commit, or describe how a private revision could be provided later. Do not paste source code.
List up to eight names and what each is intended to read, change, or call.
Operating system, language/runtime, package manager, setup command, and safe fixture availability.
For example: local desktop client over stdio, or an internal service over authenticated HTTP.
What decision should the report support? Describe sensitive data or actions without sharing them.
Return to the offer

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.