ZBS Index What actually exists in applied AI, with the source next to it

mcp server

icme-preflight

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

Description as published by the maintainer. Source

  • version 1.0.1
  • slowing

slowing — Registry entry last updated 2026-03-23.

What this server can do

14 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.

check_action(action, api_key, policy_id)
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. Required: policy_id, action, api_key.
check_action_paid(action, policy_id)
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. Required: policy_id, action.
check_logic(show_smt, reasoning)
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. Required: reasoning.
check_relevance(action, api_key, policy_id, threshold)
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. Required: policy_id, action, api_key.
create_account(username)
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. Required: username.
create_account_card(username)
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. Required: username.
get_scenarios(api_key, policy_id)
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. Required: policy_id, api_key.
make_rules(policy, api_key)
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. Required: policy, api_key.
poll_session(session_id)
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. Required: session_id.
quick_check(action, api_key, policy_id)
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. Required: policy_id, action, api_key.
run_tests(api_key, policy_id)
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. Required: policy_id, api_key.
top_up(api_key)
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. Required: api_key.
top_up_card(api_key, amount_usd)
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. Required: amount_usd, api_key.
verify_proof(proof_id)
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. Required: proof_id.

Last successful function declaration observed on . Source: https://api.icme.io/mcp. We list what the server declared; we do not call any of these functions.

Endpoint status observed on . Source: https://api.icme.io/mcp.

Signals

These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.

Signal Value What it measures Window Observed Source
Latest published version 1.0.1 Latest version string the maintainer published to the registry. as of fetch Model Context Protocol
Registry record last updated 2026-03-23 When the registry record was last updated by its maintainer. point in time Model Context Protocol
First listed in the MCP Registry 2026-03-23 Date this server was first published to the official MCP Registry. Not a usage or quality measure. point in time Model Context Protocol
mcp tools declared 14 tools Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. as of probe api.icme.io
mcp endpoint status ok The server listed 14 functions when asked. as of probe api.icme.io

Where to get it

This record as data

Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.

GET /api/v1/entries/mcp_server.json

Sources

  1. Tools declared by the MCP server at https://api.icme.io/mcp — api.icme.io, observed , trust tier 1.
  2. Official MCP Registry — Model Context Protocol, observed , trust tier 1.