io.github.wyattbenno777/icme-preflight
REMOTE · API.ICME.IO · SCANNED SEP 20
Jailbreak-proof AI guardrails. Automated Reasoning SMT solver, not an LLM. ZK proofs included.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1492 tokens (~106/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.wyattbenno777/icme-preflight MCP server?
io.github.wyattbenno777/icme-preflight is a hosted endpoint at https://api.icme.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.icme.io
claude mcp add --transport http wyattbenno777-icme-preflight 'https://api.icme.io/mcp'
{
"mcpServers": {
"wyattbenno777-icme-preflight": {
"url": "https://api.icme.io/mcp"
}
}
} {
"servers": {
"wyattbenno777-icme-preflight": {
"type": "http",
"url": "https://api.icme.io/mcp"
}
}
} [mcp_servers.wyattbenno777-icme-preflight] url = "https://api.icme.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"wyattbenno777-icme-preflight": {
"type": "remote",
"url": "https://api.icme.io/mcp",
"enabled": true
}
}
} openclaw mcp add wyattbenno777-icme-preflight --url 'https://api.icme.io/mcp' --transport streamable-http
mcp_servers:
wyattbenno777-icme-preflight:
url: "https://api.icme.io/mcp" {
"McpServers": {
"wyattbenno777-icme-preflight": {
"Transport": "http",
"Url": "https://api.icme.io/mcp"
}
}
} assistant mcp add wyattbenno777-icme-preflight -t streamable-http -u 'https://api.icme.io/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.icme.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=icme.io | CN=WE1,O=Google Trust Services,C=US | 18 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 8385e0f3c4f75ad30e0bf4e3496a7035 |
| SANs: icme.io, *.icme.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.icme.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| icme.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.icme.io/mcp | Verified | 200 | |
| http (plaintext) | http://api.icme.io/mcp | HTTPS enforced | 301 | https://api.icme.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_action ~158
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 | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
check_action_paid ~110
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 | Type | Req | Description |
|---|---|---|---|
| action | string | yes | The agent action to verify against the policy (max 2000 chars) |
| policy_id | string | yes | Policy ID from make_rules |
No output schema declared.
No examples provided.
check_logic ~153
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 | Type | Req | Description |
|---|---|---|---|
| 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 | – | Include the generated SMT-LIB2 formula in the response for inspection (default: false) |
No output schema declared.
No examples provided.
check_relevance ~149
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 | Type | Req | Description |
|---|---|---|---|
| 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 | – | Relevance threshold (0.0 to 1.0). Default 0.0 — any match triggers should_check. Optional. |
No output schema declared.
No examples provided.
create_account ~85
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 | Type | Req | Description |
|---|---|---|---|
| username | string | yes | Unique username (1-32 chars, alphanumeric + hyphens/underscores) |
No output schema declared.
No examples provided.
create_account_card ~81
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 | Type | Req | Description |
|---|---|---|---|
| username | string | yes | Unique username (1-32 chars, alphanumeric + hyphens/underscores) |
No output schema declared.
No examples provided.
get_scenarios ~72
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 | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your ICME API key |
| policy_id | string | yes | Policy ID from make_rules |
No output schema declared.
No examples provided.
make_rules ~154
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 | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
poll_session ~68
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 | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | The session_id returned by create_account_card or top_up_card |
No output schema declared.
No examples provided.
quick_check ~113
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 | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
run_tests ~72
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 | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your ICME API key |
| policy_id | string | yes | Policy ID to test |
No output schema declared.
No examples provided.
top_up ~58
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 | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your ICME API key |
No output schema declared.
No examples provided.
top_up_card ~124
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 | Type | Req | Description |
|---|---|---|---|
| amount_usd | integer | yes | Top-up amount in USD: 5, 10, 25, 50, or 100 |
| api_key | string | yes | Your ICME API key |
No output schema declared.
No examples provided.
verify_proof ~95
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 | Type | Req | Description |
|---|---|---|---|
| proof_id | string | yes | The proof_id returned by a prior check_action or check_action_paid call |
No output schema declared.
No examples provided.
What is the io.github.wyattbenno777/icme-preflight MCP server?
io.github.wyattbenno777/icme-preflight is an MCP server listed in the public MCP registry as io.github.wyattbenno777/icme-preflight. Jailbreak-proof AI guardrails. Automated Reasoning SMT solver, not an LLM. ZK proofs included. This page covers its hosted endpoint (https://api.icme.io/mcp).
Is the io.github.wyattbenno777/icme-preflight MCP server safe to use?
io.github.wyattbenno777/icme-preflight scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.wyattbenno777/icme-preflight MCP server expose?
io.github.wyattbenno777/icme-preflight exposes 14 tools: check_logic, check_relevance, make_rules, check_action, check_action_paid, and 9 more. Their descriptions and schemas cost roughly 1,492 tokens of context every time the server is loaded.
Does the io.github.wyattbenno777/icme-preflight MCP server require authentication?
No. We connected to io.github.wyattbenno777/icme-preflight without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.wyattbenno777/icme-preflight MCP server still maintained?
io.github.wyattbenno777/icme-preflight is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.