# DeltaX Preflight (mcpb · deltax-preflight-mcp-0.1.0.mcpb)

Check finite candidate proposals against separate policy and evidence, with canonical hash receipts.

- Trust score: 47/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- mcpb · `deltax-preflight-mcp-0.1.0.mcpb`: 47/100 (this document), [markdown](https://verifymcp.io/servers/deltax-public-deltax-preflight/deltax-preflight-mcp.md), [page](https://verifymcp.io/servers/deltax-public-deltax-preflight/deltax-preflight-mcp)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/DeltaX-Public/deltax-preflight/releases/download/mcp-v0.1.0/deltax-preflight-mcp-0.1.0.mcpb`
- Transport: `stdio`
- SHA-256: `018a56917bda7aa562ac9b3fc86df856ed984e03629efd01c7c3bc24f6e05d73`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 14 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 298 tokens (~99/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the DeltaX Preflight MCP server?

DeltaX Preflight ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 018a56917bda7aa562ac9b3fc86df856ed984e03629efd01c7c3bc24f6e05d73; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/DeltaX-Public/deltax-preflight/releases/download/mcp-v0.1.0/deltax-preflight-mcp-0.1.0.mcpb`
- SHA-256: `018a56917bda7aa562ac9b3fc86df856ed984e03629efd01c7c3bc24f6e05d73`

### Verify on macOS / Linux

```bash
echo "018a56917bda7aa562ac9b3fc86df856ed984e03629efd01c7c3bc24f6e05d73  deltax-preflight-mcp-0.1.0.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\deltax-preflight-mcp-0.1.0.mcpb).Hash -eq "018a56917bda7aa562ac9b3fc86df856ed984e03629efd01c7c3bc24f6e05d73"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 47, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-04 (score 46, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 45, +1)

- [functional improvement] Maintenance: unverified → pass

### 2026-11-02 (score 44, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 43, −1)

- [functional regression] Maintenance: pass → unverified

### 2026-10-30 (score 44, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 43, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 42, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `preflight_check` (~129 tokens)

Check a decision proposal against separate policy and evidence documents using the local Preflight v2 validator. Returns the unchanged result, receipt and optional local handoff. PASS_SINGLE, REFUSE, EVIDENCE_REQUIRED and SELECTION_REQUIRED are normal results; none authorizes execution. Caller-supplied facts and policy are not independently verified.

Input parameters:

- `decision` (required): Preflight v2 decision JSON document; the core validator checks its fields.
- `evidence` (required): Preflight v2 evidence JSON document, bound to the exact decision_hash.
- `policy` (required): Preflight v2 policy JSON document from the workflow owner.

### `preflight_hash_decision` (~55 tokens)

Validate a Preflight v2 decision and compute its canonical SHA-256 decision_hash for binding separately obtained evidence. A hash does not authenticate facts or grant authority.

Input parameters:

- `decision` (required): Preflight v2 decision JSON document.

### `preflight_hash_policy` (~56 tokens)

Validate a Preflight v2 policy and compute its canonical SHA-256 policy_hash. A hash is only a trusted pin when its expected value is controlled outside the proposal.

Input parameters:

- `policy` (required): Preflight v2 policy JSON document.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/deltax-public-deltax-preflight/deltax-preflight-mcp#diagnostics

## Score history

- 2026-11-06: 47
- 2026-11-05: 46
- 2026-11-04: 46
- 2026-11-03: 45
- 2026-11-02: 44
- 2026-11-01: 43
- 2026-10-31: 44
- 2026-10-30: 44
- 2026-10-29: 43
- 2026-10-28: 43
- 2026-10-27: 42
- 2026-10-26: 42
- 2026-10-25: 41
- 2026-10-24: 41
- 2026-10-23: 40
- 2026-10-22: 40

## Common questions

### What is the DeltaX Preflight MCP server?

DeltaX Preflight is an MCP server listed in the public MCP registry as io.github.DeltaX-Public/deltax-preflight. Check finite candidate proposals against separate policy and evidence, with canonical hash receipts. This page covers its MCPB bundle (https://github.com/DeltaX-Public/deltax-preflight/releases/download/mcp-v0.1.0/deltax-preflight-mcp-0.1.0.mcpb).

### Is the DeltaX Preflight MCP server safe to use?

DeltaX Preflight scores 47 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the DeltaX Preflight MCP server expose?

DeltaX Preflight exposes 3 tools: preflight_check, preflight_hash_decision, preflight_hash_policy. Their descriptions and schemas cost roughly 240 tokens of context every time the server is loaded.

### What licence is the DeltaX Preflight MCP server under?

DeltaX Preflight declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the DeltaX Preflight MCP server?

VerifyMCP ran 12 checks on DeltaX Preflight, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about DeltaX Preflight: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/DeltaX-Public/deltax-preflight
- Changelog RSS feed: https://verifymcp.io/servers/deltax-public-deltax-preflight/deltax-preflight-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/deltax-public-deltax-preflight/deltax-preflight-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/deltax-public-deltax-preflight/deltax-preflight-mcp.json
- HTML version of this page: https://verifymcp.io/servers/deltax-public-deltax-preflight/deltax-preflight-mcp
