Preflight
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEV_MODE | No | Set to 1 to run the server in dev mode, where no wallet is needed to exercise the paid endpoints (e.g. `DEV_MODE=1 uv run uvicorn preflight.api.app:app --port 8000`). | 0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| preflight_checkA | Scan Solidity source and return a security verdict. This is a paid call ($0.01 USDC on Base mainnet) that flows through x402; in dev mode (DEV_MODE=1) no payment is required. |
| preflight_simA | Simulate a transaction against a contract and return revert reason, gas used, balance deltas, and severity-scored findings. mode='quick' costs $0.05 (eth_call); mode='deep' costs $0.25 (anvil local fork with gas, balance_delta_wei, and internal_calls). Paid in USDC on Base mainnet via x402; DEV_MODE=1 skips payment. |
| preflight_token_riskA | Check a token contract before trading it. Returns a honeypot transfer verdict, transfer tax percentage, and owner privileges as a severity-scored ScanReport. Paid call ($0.05 USDC on Base mainnet) via x402; DEV_MODE=1 skips payment. |
| preflight_pricingA | Return the Preflight service info and price list (free). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct primary target: source-code security scan, transaction simulation, token risk assessment, and pricing info. preflight_check and preflight_token_risk both return security-related reports, so an agent might occasionally need the descriptions to choose correctly, but the boundary is reasonably clear.
All four tools use a consistent preflight_ snake_case prefix followed by a clear action or resource noun. There are no mixed casing or verb-style inconsistencies.
Four tools is a well-scoped surface for a focused smart-contract preflight service. Each tool corresponds to a meaningful operation or necessary service-discovery endpoint.
The set covers the core workflows: source scanning, transaction simulation with quick/deep modes, token risk checking, and pricing discovery. Minor gaps exist around retrieving past reports, batch operations, or status/history, but the essential lifecycle is represented.