Skip to main content
Glama
DeltaX Preflight

DeltaX Preflight

Official

Related Servers

Alternatives to DeltaX Preflight

  • A
    license
    Not graded
    quality
    C
    maintenance
    Self-hosted MCP gateway that applies deterministic, compiled policy to tool discovery, invocation, and outbound data flow, with no model in the enforcement path. Every decision emits a hash-chained receipt sealed with Ed25519 and verifiable using public keys only.
    Apache 2.0

Related Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables local candidate review of ONNX or TFLite models by checking static evidence and externally measured results against a fixed policy, producing accept/reject/hold evidence ZIPs for AI agent workflows.
    Apache 2.0
  • A
    license
    B
    quality
    B
    maintenance
    Enables MCP clients to verify claims against evidence, generate and validate tamper-evident receipts, and pre-filter prompt-injection attempts through stdio JSON-RPC tools.
    5
    Apache 2.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    Read-only CLI and stdio MCP server that inventories the MCP servers an agent can reach, compiles a least-privilege policy with a reason for every allow/approve/deny verdict, and emits a delivery the recipient re-verifies in their own browser using a sha256 manifest.
    Apache 2.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables users to trace regulatory rule changes to affected parties and required actions through deterministic safety gates, returning dated action plans and hash-linked evidence records. Supports 12 MCP tools over stdio or streamable HTTP for source comparison, obligation decomposition, scope assessment, planning, and evidence validation across multiple domain packs.
    MIT

TDQS

A4.7/5.0

Scored across 3 tools

Disambiguation5/5

The three tools target clearly distinct operations: evaluating candidate actions, hashing a decision, and hashing a policy. Although the two hash tools share the 'hash' verb, their inputs and purposes are unambiguous, and the descriptions explicitly separate them.

Naming Consistency5/5

All tools use the same snake_case convention with a consistent 'preflight_' namespace prefix. The action suffixes are readable and predictable despite the slight grammatical difference between 'check' and 'hash_*'.

Tool Count5/5

Three tools are well-scoped for a narrow preflight validation server. Each tool earns its place: one evaluation operation and two canonical hashing operations for the objects the server manages.

Completeness4/5

The surface covers the core lifecycle of checking candidates and pinning policies/decisions with canonical hashes. A minor gap is that there is no separate evidence/proposal hashing or inspection tool, but the stated workflow does not strictly require one.

Maintenance

ActivityNo data
ResponsivenessOutdated data