MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Icme Preflight is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Jailbreak-proof AI guardrails. Automated Reasoning SMT solver, not an LLM. ZK proofs included.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http icme-preflight-mcp https://api.icme.io/mcp
# 2 — ask your agent for something these tools do
# check_logic, check_relevance, make_rules and 11 more
Icme Preflight costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http icme-preflight-mcp https://api.icme.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reasoning | string | yes | 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 | no | Include the generated SMT-LIB2 formula in the response for inspection (default: false) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | The agent action to screen (max 2000 chars) |
| api_key | string | yes | Your ICME API key |
| policy_id | string | yes | Policy ID from make_rules |
| threshold | number | no | Relevance threshold (0.0 to 1.0). Default 0.0 — any match triggers should_check. Optional. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | Your ICME API key (from create_account or create_account_card) |
| policy | string | yes | 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. |
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 expl
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | The agent action to verify against the policy (max 2000 chars) |
| api_key | string | yes | Your ICME API key |
| policy_id | string | yes | Policy ID from make_rules |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | The agent action to verify against the policy (max 2000 chars) |
| policy_id | string | yes | Policy ID from make_rules |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | The agent action to check (max 2000 chars) |
| api_key | string | yes | Your ICME API key |
| policy_id | string | yes | Policy ID from make_rules |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| proof_id | string | yes | The proof_id returned by a prior check_action or check_action_paid call |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | Your ICME API key |
| policy_id | string | yes | Policy ID from make_rules |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | Your ICME API key |
| policy_id | string | yes | Policy ID to test |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| username | string | yes | Unique username (1-32 chars, alphanumeric + hyphens/underscores) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| username | string | yes | Unique username (1-32 chars, alphanumeric + hyphens/underscores) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | Your ICME API key |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| amount_usd | integer | yes | Top-up amount in USD: 5, 10, 25, 50, or 100 |
| api_key | string | yes | Your ICME API key |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | The session_id returned by create_account_card or top_up_card |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Icme Preflight or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Icme Preflight can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.