01Up to 20 agreed cases
Founding evidence pilot · applications open
For teams that need evidence about a specific MCP client, partner or submission route—not a broad promise that everything is compatible.
A good pilot has edges
The first conversation is a fit check. An enquiry creates no contract, payment duty or permission to test.
A working or near-working remote MCP server
One connector, partner or marketplace route
Up to two named client or fallback paths
An authorized owner and safe test boundary
A real decision the evidence needs to support
Fixed commercial scope
01Up to 20 agreed cases
02One isolated environment
03Dated report and requirements matrix
04Evidence index with PASS, FAIL, BLOCKED and UNKNOWN
05Fix-acceptance checks
06One agreed re-test within 30 days
Access ceiling
We prefer staging, sandbox or a disposable fixture. Access is limited to named endpoints, one dedicated test identity, accepted roles and agreed cases. Credentials are transferred outside the enquiry form and deleted on the agreed schedule.
Before any test
Identify the contracting party and authorized technical contact.
Confirm control of every target and third-party permission where required.
Freeze server, client, environment and version identifiers.
Name endpoints, identity, roles, permissions and test window.
Accept cases, rate limits, exclusions and stop conditions.
Agree credential transfer, evidence handling and deletion.
Accept the written schedule and clear the first invoice.
Stop means stop
Evidence ownership and publication
The customer receives the report and evidence under the engagement terms. Customer names, private findings and identifiable test data stay private unless a separate written approval is given after delivery.
No compatibility statement exists.
PASS, FAIL, BLOCKED and UNKNOWN stay attached to exact scope.
Silence is never treated as consent.
Have an authorized target?
SCOPE SHA-256
b653dc26226799116a225a90c871966dbc6af2daba5240ce47bfcb98eaef3625