An independent assessment of your MCP server records how it handles sign-in, what it exposes without a credential, and what changes when you ship a fix. The report carries a hash a second party can recompute by re-running the same checks on the same server, so your buyer can verify it instead of trusting it.
One server, 1750 dollars. Full assessment with one retest, 3500 dollars.
One MCP server or a small set of endpoints. Written scope and authorization before testing, evidence-backed findings, a written report signed by the named researcher, and one retest of the same endpoint after fixes.
Fifteen probes returned no verdict on this target. Twelve of them share one reason: the server publishes no authorization server, so the OAuth discovery, issuer, token and client-registration checks had nothing to test against. They are recorded as excluded, not passed, and the report says so on its face.
The hash covers graded content only, the probe results, findings, severities and the basis for each severity, and leaves out timestamps and server-varying headers. A second party can re-run the same probe set on the same target and either recompute the same hash or name the fields that differ.
Send the server URL and who authorizes the test. Scope and written authorization are agreed by email before anything is tested. Do not include credentials, tokens or secrets in email.
A report is a claim by someone with an interest in it being believed. The record should make that claim inspectable.
The report carries a hash over the graded content. With written authorization, a second party can re-run the same probe set and compare. The comparison is recorded as MATCH, DIVERGENCE or NOT REPRODUCIBLE.
The method does not claim the tool or report is right; it makes inconsistencies easier to catch. Reproduction depends on the agreed scope, available access, and supported techniques.
Who signs the report
Leroy H. Mason
Independent AI security researcher, credited reporter on published MCP security advisories. The assessment is a scoped technical review, not a certification, guarantee of security, or promise of buyer acceptance.
The MIT-licensed mcp-authscan is available on GitHub and PyPI. Its free scanner checks the handshake; paid work adds an authorized tool-call check and a named written report within the agreed scope.
Inspect the tool
Start with the same public checks.
The paid check is performed only with written authorization and where the agreed scope and supported techniques allow it. Neither an authorized tool-call check nor a particular coverage outcome is guaranteed before scope is agreed; no test is represented as already run.