# io.github.wyattbenno777/icme-preflight (remote · api.icme.io)

Jailbreak-proof AI guardrails. Automated Reasoning SMT solver, not an LLM. ZK proofs included.

- Trust score: 64/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.icme.io`: 64/100 (this document), [markdown](https://verifymcp.io/servers/wyattbenno777-icme-preflight/api.md), [page](https://verifymcp.io/servers/wyattbenno777-icme-preflight/api)

## Channel facts

- Endpoint: `https://api.icme.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 14 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1492 tokens (~106/item across 14 items; 14 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http wyattbenno777-icme-preflight https://api.icme.io/mcp
```

### Codex

```toml
[mcp_servers.wyattbenno777-icme-preflight]
url = "https://api.icme.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyattbenno777-icme-preflight": {
      "type": "remote",
      "url": "https://api.icme.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add wyattbenno777-icme-preflight --url https://api.icme.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  wyattbenno777-icme-preflight:
    url: "https://api.icme.io/mcp"
```

### Other

```json
{
  "mcpServers": {
    "wyattbenno777-icme-preflight": {
      "type": "http",
      "url": "https://api.icme.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-08-02 (score 64, +1)

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

### 2026-07-31 (score 63, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 63, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 63, +1)

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

### 2026-07-27 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 61)

First indexed and scored.

## MCP tools (14)

### `check_logic` (~153 tokens)

Catch contradictions in reasoning before acting on it. FREE — no account needed. Extracts quantitative and logical claims from any plan, calculation, or chain of thought, then uses a Z3 SAT solver to mathematically prove whether they contradict each other. This is formal verification, not an LLM second-guessing itself. Returns CONSISTENT, CONTRADICTION, or UNKNOWN with the extracted claims.

Input parameters:

- `reasoning` (string, required): The reasoning, plan, or chain of thought to check. Be specific — include numbers, conditions, and constraints for the best results (max 2000 chars)
- `show_smt` (boolean): Include the generated SMT-LIB2 formula in the response for inspection (default: false)

### `check_relevance` (~149 tokens)

Free relevance screen — checks whether an action touches any of your policy variables before running a paid check. Returns a relevance score and which variables matched. If should_check is true, run check_action. If false, the action is unrelated to your policy — skip the paid check. No credits charged. Requires api_key.

Input parameters:

- `action` (string, required): The agent action to screen (max 2000 chars)
- `api_key` (string, required): Your ICME API key
- `policy_id` (string, required): Policy ID from make_rules
- `threshold` (number): Relevance threshold (0.0 to 1.0). Default 0.0 — any match triggers should_check. Optional.

### `make_rules` (~154 tokens)

Turn a plain-English policy into a jailbreak-proof guardrail. Write rules the way you would explain them to a colleague — ICME compiles them into formal logic (SMT-LIB) that a mathematical solver enforces. No prompt engineering. No LLM judges. The solver either proves an action complies or it doesn't. Returns a policy_id and test scenarios for review. Costs 300 credits. Requires api_key.

Input parameters:

- `api_key` (string, required): Your ICME API key (from create_account or create_account_card)
- `policy` (string, required): Your policy in plain English, e.g. 'No action may access user data without explicit consent. External API calls require approval above $100.' Up to 50 rules.

### `check_action` (~158 tokens)

Enforce a guardrail: verify an agent action against a compiled policy using formal verification. An SMT solver — not an LLM — determines whether the action satisfies every rule. Returns SAT (allowed) or UNSAT (blocked) with extracted values and a cryptographic ZK proof that the check was performed correctly. Cannot be jailbroken. 1 credit ($0.01). Requires api_key. Tip: end the action with an explicit claim like 'I assert this complies with the policy' for best extraction.

Input parameters:

- `action` (string, required): The agent action to verify against the policy (max 2000 chars)
- `api_key` (string, required): Your ICME API key
- `policy_id` (string, required): Policy ID from make_rules

### `check_action_paid` (~110 tokens)

Same formal verification as check_action, but pay per call with x402 ($0.10 USDC on Base) instead of using credits. No API key or account needed — any agent with a wallet can verify actions on the fly. Returns SAT (allowed) or UNSAT (blocked) with extracted values and optional ZK proof.

Input parameters:

- `action` (string, required): The agent action to verify against the policy (max 2000 chars)
- `policy_id` (string, required): Policy ID from make_rules

### `quick_check` (~113 tokens)

Fast yes/no guardrail verdict — returns only ALLOWED or BLOCKED with no proof details. Use when you need a lightweight gate and don't need the full SAT/UNSAT report or ZK proof. Same formal verification under the hood, just a minimal response. 1 credit. Requires api_key.

Input parameters:

- `action` (string, required): The agent action to check (max 2000 chars)
- `api_key` (string, required): Your ICME API key
- `policy_id` (string, required): Policy ID from make_rules

### `verify_proof` (~95 tokens)

Independently verify a ZK proof from a prior check_action call. Confirms the guardrail check was performed correctly without re-running it — any third party or monitoring agent can verify in under one second. No additional cost. Wait a few minutes after the check for the proof to be generated. Single-use per proof.

Input parameters:

- `proof_id` (string, required): The proof_id returned by a prior check_action or check_action_paid call

### `get_scenarios` (~72 tokens)

Review auto-generated test scenarios for a compiled policy. Shows example actions that should pass and fail, so you can verify the policy behaves as intended before deploying it. Requires api_key.

Input parameters:

- `api_key` (string, required): Your ICME API key
- `policy_id` (string, required): Policy ID from make_rules

### `run_tests` (~72 tokens)

Run saved test cases against a policy to confirm it blocks what it should block and allows what it should allow. Run this after make_rules and before using the policy in production. Requires api_key.

Input parameters:

- `api_key` (string, required): Your ICME API key
- `policy_id` (string, required): Policy ID to test

### `create_account` (~85 tokens)

Create an ICME Preflight account with x402 USDC payment ($5.00 on Base). Returns an API key and 325 starting credits immediately. Save the api_key — it is shown only once. Use create_account_card instead if paying by credit card.

Input parameters:

- `username` (string, required): Unique username (1-32 chars, alphanumeric + hyphens/underscores)

### `create_account_card` (~81 tokens)

Create an ICME Preflight account with a credit card ($5.00 via Stripe). Returns a checkout_url — open it in a browser to pay. After payment completes, call poll_session with the session_id to retrieve your API key.

Input parameters:

- `username` (string, required): Unique username (1-32 chars, alphanumeric + hyphens/underscores)

### `top_up` (~58 tokens)

Add 500 credits to your account via x402 USDC payment ($5.00 on Base). Use top_up_card instead for credit card payment with volume discounts. Requires api_key.

Input parameters:

- `api_key` (string, required): Your ICME API key

### `top_up_card` (~124 tokens)

Add credits via credit card with volume bonuses. Returns a checkout_url. Tiers: $5 = 500 credits, $10 = 1,050 (+5%), $25 = 2,750 (+10%), $50 = 5,750 (+15%), $100 = 12,000 (+20%). Credits never expire. Requires api_key.

Input parameters:

- `amount_usd` (integer, required): Top-up amount in USD: 5, 10, 25, 50, or 100
- `api_key` (string, required): Your ICME API key

### `poll_session` (~68 tokens)

Check the status of a Stripe card payment. Returns pending or complete. On completion after signup, returns the api_key. Call this after create_account_card or top_up_card once the user has paid.

Input parameters:

- `session_id` (string, required): The session_id returned by create_account_card or top_up_card

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/wyattbenno777-icme-preflight/api#diagnostics

## Score history

- 2026-08-03: 64
- 2026-08-02: 64
- 2026-08-01: 63
- 2026-07-31: 63
- 2026-07-30: 63
- 2026-07-29: 63
- 2026-07-28: 62
- 2026-07-27: 62
- 2026-07-26: 61

## Links

- Remote endpoint: https://api.icme.io/mcp
- Repository: https://github.com/ICME-Lab/smt-ar-base
- Changelog RSS feed: https://verifymcp.io/servers/wyattbenno777-icme-preflight/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyattbenno777-icme-preflight/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/wyattbenno777-icme-preflight/api