Independent MCP compatibility reviews
Find the connection, sign-in, and tool behaviour gaps
before your next client or marketplace review.
US$495 standard scope · written authorization required · no checkout
In this fictional case, the client starts authentication but the return step has not been demonstrated.
The PDF documents a separate fictional local test, not a real-client assessment. Read the methodology and evidence.
Read the sample PDFWhat lands with your team
A requirements matrix for the route you name, with dated sources and anything still unknown.
Named test cases with the relevant requests, responses, versions, and limits. An evidence index keeps it traceable.
A written conclusion, practical fix checks, and one re-test. No universal compatibility score.
Small enough to be specific
Best for a working or near-working remote MCP server with a real client, partner, or submission route in view.
If you need the server built, a penetration test, or certification, this isn’t that service.
Tell us the target and what your team needs to decide.
Cases, permission, exclusions, access, timing, and terms—before payment or testing.
Receive the report, work through the findings, and use your included re-test.
Independent reviews · South Africa
Start with the target you’re working toward and the decision you need to make. The scope sets out what can be checked and what is excluded.
Each conclusion is limited to the recorded cases, versions and environment. The review does not speak for any platform or promise approval.
How the review worksNo. This is an independent review of the cases we agree to test. It is not a security audit, platform endorsement, or guarantee of marketplace acceptance.
Start with the client or submission route you care about, a public link if you have one, and the decision you need to make. Keep credentials and private customer data out of the enquiry.
After we both accept the written scope, the first invoice clears, and the agreed access is ready. Any dependency that changes the timing is recorded in the scope.
One agreed re-test is included within 30 days of delivery. New clients, new requirements, or a different test boundary need a new scope.
Have a target in mind?