Skip to content

icme-preflight MCP server

io.github.wyattbenno777/icme-preflightwyattbenno777streamable-httpv1.0.1Scanned

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

14 tools: 13 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 13 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

13 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the icme-preflight MCP server can do

The icme-preflight MCP server is published by the GitHub account wyattbenno777. It has 14 tools. It can create or change data (13 tools: check_logic, check_relevance, make_rules, check_action and 9 more), but cannot delete data. 1 tool only reads.

1 tool brings in text other people can write (get_scenarios).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

14 tools

Changes things 13Claude Code: ask
  • check_actionEnforce a guardrail: verify an agent action against a compiled policy using formal verification.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • check_action_paidSame formal verification as check_action, but pay per call with x402 ($0.10 USDC on Base) instead of using credits.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • check_logicCatch contradictions in reasoning before acting on it.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • check_relevanceFree relevance screen — checks whether an action touches any of your policy variables before running a paid check.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • create_accountCreate an ICME Preflight account with x402 USDC payment ($5.00 on Base).No findings

    Why it is in this group

    • The name "create_account" says "create": a word for a change.
    Description, as the server wrote it
    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.
  • create_account_cardCreate an ICME Preflight account with a credit card ($5.00 via Stripe).No findings

    Why it is in this group

    • The name "create_account_card" says "create": a word for a change.
    Description, as the server wrote it
    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.
  • make_rulesTurn a plain-English policy into a jailbreak-proof guardrail.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • poll_sessionCheck the status of a Stripe card payment.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • quick_checkFast yes/no guardrail verdict — returns only ALLOWED or BLOCKED with no proof details.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • run_testsRun saved test cases against a policy to confirm it blocks what it should block and allows what it should allow.No findings

    Why it is in this group

    • The name "run_tests" says "run": a word for a change.
    Description, as the server wrote it
    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.
  • top_upAdd 500 credits to your account via x402 USDC payment ($5.00 on Base).No findings

    Why it is in this group

    • The description's first verb is "add": a word for a change.
    Description, as the server wrote it
    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.
  • top_up_cardAdd credits via credit card with volume bonuses.No findings

    Why it is in this group

    • The description's first verb is "add": a word for a change.
    Description, as the server wrote it
    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.
  • verify_proofIndependently verify a ZK proof from a prior check_action call.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 1Show 1 read-only tool
  • get_scenariosReview auto-generated test scenarios for a compiled policy.Reads text others writeNo findings

    Why it is in this group

    • The name "get_scenarios" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:13 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
13
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 13 tools that change things (13 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.icme.io/mcp: tools/list returned 14 tools to an anonymous client, including check_logic (write), check_relevance (write), make_rules (write), check_action (write), check_action_paid (write) and 8 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__icme-preflight__get_scenarios"
    ],
    "ask": [
      "mcp__icme-preflight__check_logic",
      "mcp__icme-preflight__check_relevance",
      "mcp__icme-preflight__make_rules",
      "mcp__icme-preflight__check_action",
      "mcp__icme-preflight__check_action_paid",
      "mcp__icme-preflight__quick_check",
      "mcp__icme-preflight__verify_proof",
      "mcp__icme-preflight__run_tests",
      "mcp__icme-preflight__create_account",
      "mcp__icme-preflight__create_account_card",
      "mcp__icme-preflight__top_up",
      "mcp__icme-preflight__top_up_card",
      "mcp__icme-preflight__poll_session"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as icme-preflight. Review it before you use it.

Capability tags behind 1 rule
  • mcp__icme-preflight__get_scenarios untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.wyattbenno777/icme-preflight/verify?hash=ff9db31dc62bbd7e902f50541e432bddb5935cac84b6d45a0c2ec0603a9af437" | jq -e '.changed == false'

Pinned hash ff9db31dc62b, from Nov 20, 2026, 18:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.wyattbenno777/icme-preflight/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.wyattbenno777/icme-preflight
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.wyattbenno777/icme-preflight.svg)](https://radar.anlyon.com/servers/io.github.wyattbenno777/icme-preflight)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:51 UTC.

icme-preflight MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the icme-preflight MCP server safe?

No scan can promise that. What its definitions show: 14 tools, 13 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the icme-preflight MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the icme-preflight MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the icme-preflight MCP server have?

14 tools: 13 write, 1 read. check_logic, check_relevance, make_rules, check_action, check_action_paid, quick_check, verify_proof, run_tests and 6 more.

Does the icme-preflight MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the icme-preflight MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the icme-preflight MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.