isWebMCP

Vercel · Deployment workflows and integrations · Uncontacted prospect

Make source evidence part of a release

Proposed design partnership: help one team keep a public-page baseline with each release. Start with our existing CI workflow, not a claim of a native Marketplace integration.

Documented by the company

What the official sources establish

Why this prospect: 9/10 editorial fit

Editorial inference, 9/10: the existing CLI/CI path can support a narrow public deployment pilot now. A documented integration channel is reusable, but native onboarding and runtime evidence are additional work, not present capabilities. This is our prioritization judgment, not a company-quality score or evidence of adoption.

Current product fit
2 / 2
Documented integration path
2 / 2
Reusable integration
2 / 2
Pilot feasibility
2 / 2
Future runtime fit
1 / 2
Read the selection method →

Proposed integration—not a validated connector

  • An owner chooses one already-public, stable URL with useful server-returned HTML. Run the isWebMCP CLI after the deployment becomes ready, then retain the summary JSON as their CI artifact.
  • After a reviewed fix reaches that same URL, compare complete reports with the same scanner model and input fingerprint. Treat commit-specific preview URLs as separate targets; never rewrite their identity to force a comparison.
  • Start in advisory mode. A later project-scoped integration could attach findings to deployment checks only after installation, deletion, authentication, and failure-handling flows are implemented and tested.

What we can supply now

  • Public HTML scans, supported starter recipes, and developer-controlled GitHub Actions jobs.
  • Local comparison of compatible saved JSON reports; no Vercel account credential is required for a public-page pilot.

What needs development or partner agreement

  • Native project selection, signed webhook handling, durable tenant-scoped evidence, and a Marketplace review package.
  • An authorized private runner before protected previews are eligible; never disable protection to make an audit work.

Proposed pilot · Not performed

A bounded way to test the hypothesis

Proposed scope, not a commitment: one consenting application team, one stable public search or form page, and two successive releases.

Deliverables to produce

  • A reproducible CI example, baseline/current artifacts, and a finding-to-fix review note.
  • A small integration specification describing advisory failures, retries, and target identity.

Measures to collect—not results

  • Record setup time, complete-run count, and valid-comparison count with denominators.
  • Ask whether the owner used a finding in a reviewed change and voluntarily reran the check on the next release.

Stop or decline if…

  • Stop if the only meaningful target is protected or client-rendered content absent from returned HTML.
  • Do not block a release on an uncalibrated score or equate fewer source findings with task success.

Risks and open diligence questions

  • Changing preview URLs, caching, redirects, or analysis inputs can invalidate comparisons.
  • Current service limits and lack of an SLA make broad release-blocking promises premature.

Public route for a future conversation

The official checklist publishes integrations@vercel.com for review requests. Use it only for a qualified integration inquiry; no application or email has been sent. No message or application has been sent for this proposal.

Official integration review route ↗

Source and date ledger

Research reviewed 2026-09-05. Dates describe the source, not a company trial. An unavailable publication date is left unknown.