icme-preflight
Server Details
Jailbreak-proof AI guardrails. Automated Reasoning SMT solver, not an LLM. ZK proofs included.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.2/5 across 14 of 14 tools scored. Lowest: 3.3/5.
Most tools have distinct purposes, such as check_action for formal verification, make_rules for policy creation, and get_scenarios for testing. However, check_action and quick_check both provide guardrail verdicts, with quick_check being a lightweight version, which could cause some confusion if an agent doesn't carefully read the descriptions. The paid vs. free variants (e.g., check_action vs. check_action_paid) are clearly differentiated by payment method.
Tool names follow a consistent snake_case pattern throughout, with clear verb_noun structures like check_action, create_account, and run_tests. This predictability makes it easy for an agent to understand and navigate the toolset without confusion from mixed naming conventions.
With 14 tools, the set is well-scoped for a policy verification and account management server. It covers core workflows from policy creation (make_rules) to verification (check_action, quick_check), testing (run_tests, get_scenarios), and account operations (create_account, top_up), with each tool serving a clear purpose without redundancy.
The toolset provides complete coverage for the domain of policy enforcement and verification. It includes policy creation (make_rules), verification with different options (check_action, quick_check, check_logic), testing (run_tests, get_scenarios), account management (create_account, top_up), and proof verification (verify_proof). There are no obvious gaps, and agents can handle the full lifecycle from setup to enforcement.
Available Tools
14 toolscheck_actionInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | The agent action to verify against the policy (max 2000 chars) | |
| api_key | Yes | Your ICME API key | |
| policy_id | Yes | Policy ID from make_rules |
check_action_paidInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | The agent action to verify against the policy (max 2000 chars) | |
| policy_id | Yes | Policy ID from make_rules |
check_logicInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| show_smt | No | Include the generated SMT-LIB2 formula in the response for inspection (default: false) | |
| reasoning | Yes | The reasoning, plan, or chain of thought to check. Be specific — include numbers, conditions, and constraints for the best results (max 2000 chars) |
check_relevanceInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | The agent action to screen (max 2000 chars) | |
| api_key | Yes | Your ICME API key | |
| policy_id | Yes | Policy ID from make_rules | |
| threshold | No | Relevance threshold (0.0 to 1.0). Default 0.0 — any match triggers should_check. Optional. |
create_accountInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| username | Yes | Unique username (1-32 chars, alphanumeric + hyphens/underscores) |
create_account_cardInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| username | Yes | Unique username (1-32 chars, alphanumeric + hyphens/underscores) |
get_scenariosInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | Your ICME API key | |
| policy_id | Yes | Policy ID from make_rules |
make_rulesInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| policy | 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. | |
| api_key | Yes | Your ICME API key (from create_account or create_account_card) |
poll_sessionInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes | The session_id returned by create_account_card or top_up_card |
quick_checkInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | The agent action to check (max 2000 chars) | |
| api_key | Yes | Your ICME API key | |
| policy_id | Yes | Policy ID from make_rules |
run_testsInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | Your ICME API key | |
| policy_id | Yes | Policy ID to test |
top_upInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | Your ICME API key |
top_up_cardInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | Your ICME API key | |
| amount_usd | Yes | Top-up amount in USD: 5, 10, 25, 50, or 100 |
verify_proofInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| proof_id | Yes | The proof_id returned by a prior check_action or check_action_paid call |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!