Security Preflight · v1.2

Check the MCP integration.
Before you connect it.

Inspect the manifest, tool schemas, authority policy, and sample text you supply. Get a signed assessment that makes declared risks and gaps visible before an integration changes.

Inspect a free quote Try the free change check

$1 USDC per paid assessment. An eligible introductory quote may be $0.01. The fresh quote governs the price; the buyer authorizes every purchase.

Static artifact assessment. It does not fetch, execute, or certify the deployed runtime.

What the assessment covers

Make declared authority inspectable.

Manifest and schemas

Endpoint and authentication declarations, tool input schemas, and whether inputs are bounded by the declared schema.

Tool policy

High-impact actions, approval requirements, and conflicts between allowed, denied, and approval-required tools.

Sample text

Static injection indicators in the supplied text. Coverage is limited to the artifacts you provide.

What you receive

A result you can inspect and retain.

A verdict and individual findings.
Digests binding the assessment to your manifest, policy, and samples.
A signed, input-redacted assessment receipt.
A delivery receipt on a successful paid HTTP response.

Raw supplied artifacts are not stored in the assessment record. A receipt proves its signed contents; buyer acceptance and real-world usefulness are separate judgments.

Assessment structure

{
  "verdict": "pass | review | fail",
  "evidence": {"checks": ["individual findings"]},
  "receipt": {
    "receipt_id": "returned assessment ID",
    "evidence_sha256": "bound evidence digest",
    "expires_at": "assessment expiry"
  },
  "signature_b64": "returned signature"
}

Shortened response shape, not an executed assessment. Read an actual public receipt at /security-preflight/receipts/{receipt_id}.

Use it when something changes

Keep the baseline. Recheck what changed.

Connect the free comparison to your own release event or scheduler. Unchanged, current inputs reuse the assessment and retain any existing findings. Changed inputs, an expired assessment, or a new scanner version require a fresh assessment.

git clone https://github.com/jdhart81/viridis-agent-fleet.git
cd viridis-agent-fleet
python3 scripts/viridis_preflight_watch.py \
  --base-url https://mcp.viridis-security.com \
  --inputs examples/security-preflight-inputs.json

The example returns BASELINE_REQUIRED and quote instructions. It does not create a scan or payment. Replace the example with your current inputs, then supply the saved paid result on later checks.

Read the complete change-check recipe →

For agent builders

Choose your existing client.

MCP endpoint:

https://mcp.viridis-security.com/security-preflight/mcp

Paid HTTP endpoint:

POST /x402/security-preflight/security_preflight

OpenAPI · Machine-readable service · Agent guide

Before you authorize a purchase

Choose a real manifest and the policy it should satisfy.
Send the intended paid request without a signature to inspect its HTTP 402 quote.
Apply your own budget and payment mandate before signing.
Inspect the result, retain the receipt, and recheck after a relevant change.

The free change check is not a managed monitoring subscription. A failed assessment remains failed when unchanged.

Need help making a whole workflow reliable?

The Agent Reliability Sprint is a separately scoped implementation service for one existing workflow. Security Preflight is the bounded artifact check you can integrate directly.