The target path, translated into checks.
A dated matrix maps the selected client or submission route to evidence, gaps, and unknowns.
MCP launch readiness, made concrete
Find the gaps before the real review.
A fixed-scope review for teams taking a remote MCP server toward a named client, connector, partner, or marketplace path. You get dated evidence, clear boundaries, and fix checks your team can use.
Scope before paymentNo secrets in the formNo approval guarantee
Method foundation
A bounded public research run shaped the evidence format—not a claim of customer demand.
153declared endpoints checked once
23bounded discovery signals observed
0credentials or tool calls used
The service
Evidence for the decision in front of you.
The review is deliberately narrow: one real target path, a written boundary, and deliverables that can move from product to engineering without translation.
Findings your engineers can reproduce.
Named cases keep requests, responses, limits, timestamps, and interpretation together.
A practical next move, not a vague score.
Every actionable gap ends with a fix check, an owner-ready explanation, and a bounded conclusion.
See the structure before you enquire. The public sample shows the report style, evidence index, and limits of the conclusion.
Open sample PDFIncluded in the fixed scope
- One buyer-selected connector, client, or marketplace path
- The current remote MCP connection path and up to two named clients
- Up to 20 agreed authentication, tool, error, and limit cases
- A written report, machine-readable evidence index, and requirements matrix
- One agreed re-test within 30 days
Who should buy this
A real target. A real decision. A reviewable boundary.
This is for product and engineering teams that are close enough to launch that evidence can change the next move.
- You have a working or near-working remote MCP server.
- A real buyer, client, partner, or marketplace path is in view.
- Your team can authorize the exact test boundary in writing.
- You need evidence that helps a go / fix / pause decision.
- You need the MCP server built from scratch.
- You want penetration testing, certification, or guaranteed approval.
- There is no named target path or business decision yet.
- Testing would require access you are not authorized to provide.
How the engagement works
No access or payment until the boundary is clear.
- 01Request a fit check
Name the target path, timing, and decision. The form asks for no secrets.
- 02Agree the scope
You receive the cases, authorization, exclusions, safe-access plan, timing, and terms in writing.
- 03Run the review
The 48-hour delivery window starts after the accepted scope, cleared first invoice, and required access.
- 04Act and re-test
Your team receives the pack and one agreed re-test within 30 days.
About the practice
Built for the space between “it runs” and “it is ready.”
Connector Readiness Lab is an independent South African review practice for remote MCP products. It does not represent a platform, marketplace, or certification body.
Turn ambiguous integration requirements into evidence a team can act on.
Small product teams should be able to approach high-stakes connector reviews with clarity—not guesswork.
Say exactly what was tested, what was not, and what would change the conclusion.
Straight answers
Before you send a request.
Is this a certification or marketplace approval?
No. It is an independent, fixed-scope readiness review. The report describes the tested evidence and cannot speak for any platform or guarantee acceptance.
Do we send credentials in the request form?
No. The first request contains only business context and public links. If private testing is later agreed, the written scope defines a safer access route and stop conditions.
What if the review is not a fit?
We say so before payment. The fit check exists to avoid selling a review when the target, authority, access, or decision is not ready.
Why review only one target path?
A named path produces a defensible answer. Broad “works everywhere” claims create false confidence and weak evidence.
Start with fit, not payment
Name the target. Get a clear scope.
The form saves your request securely. If the target is not review-ready, we say so before money or private access changes hands.