Know the target.
Patch your MCP.
Prove it works.

01Why 07-28-2026 matters

The protocol surface moves.

MCP is an evolving specification. As the protocol surface and its authorization requirements change, an implementation that conformed last quarter can drift out of conformance without any change to your own code.

The 07-28-2026 target is the reference point this offer is calibrated to. The work is about implementation readiness — not alarm: confirming that authorization behavior, transport and state handling, request metadata handling, discovery, and token validation match the requirements that actually apply to your deployment.

Scope is your MCP implementation and its conformance posture. High-level engineering offer, not legal advice.

02What we check

A conformance grid, honestly labeled.

Each check is tagged so you always know whether it comes from the protocol, from common industry practice, or from PrestigeSF's own defensive posture. We do not present defensive policy as a protocol mandate.

Categorization reflects our assessment framework and is verified against the current MCP specification at engagement time. Where the spec is silent, an item is labeled Industry or Defensive — never Spec.

03The free MCP patch

The front door is free.

Start with a free, inspect-before-connect MCP patch. It runs against your own server so you can see where you stand before any conversation about paid work. The patch is the proof, not the pitch.

1. Free entry point. No invoice, no commitment. The patch is yours to run and keep.
2. Inspect before connect. You inspect your MCP surface locally, on infrastructure you already control.
3. What you receive. A runnable snippet plus a plain read on how your implementation lines up with the 07-28-2026 target.
4. If issues are found. Only then does a scoped, priced engagement make sense — assessment, then remediation where it is actually warranted.

04MCP 07-28-2026 findings

What an assessment returns.

After a scoped assessment, you receive a structured read of where your MCP implementation stands. Deliverables depend on your deployment and are confirmed at engagement — we do not promise evidence an assessment does not actually generate.

Where appropriate, output can align to the standardized DeadlineSF AI Trust Report format so MCP findings sit alongside your broader rule posture.

05Remediation

From gap to fix.

Identifying the gap is half the job. PrestigeSF can move from the finding to the applicable implementation fix — scoped and concrete, verified after the change.

1. Authorization-flow remediation — bring auth and scope step-up behavior into line with the target.
2. Request / state handling fixes — correct transport and state-boundary behavior.
3. DCR corrections where applicable — application_type and dynamic client registration handling.
4. Policy / control implementation — install the defensive controls you choose to adopt, clearly marked as policy.
5. Verification after remediation — re-check the fixed surface so the change is provable, not assumed.

06Monitoring

Requirements keep moving.

MCP requirements continue to evolve. Optional ongoing monitoring watches for material MCP changes and future DeadlineSF law-pack / spec updates, so a conformant implementation stays that way.

Monitoring is optional. You never have to buy monitoring to use the free patch.

07DeadlineSF connection

08Packages & engagement

Free patch first. Priced only where needed.

The free patch is the front door and stays free. Paid work is scoped to what the assessment actually finds.

PRESTIGE-MCP · CONFORMANCE RECEIPT · SAMPLE
target        : MCP 07-28-2026
scope         : your MCP implementation
authorization : PASS
scope step-up : PASS
transport     : PASS
discovery     : review — see findings
evidence      : attached where generated
status        : illustrative sample only

Prices shown are the existing PrestigeMCP prices — nothing here is newly invented. Sample receipt is illustrative. High-level product only — not legal advice. Sister site to DeadlineSF.net.