_ registry / mcp streamable-http · checked 1h ago

icme-preflight

https://api.icme.io

Registry code: b69b381f1b3f624e

api record

Cryptographic guardrails for AI agents. Verify actions with formal logic and zero-knowledge proofs.

from a public catalogue that lists it, not from the operator

endpoint
https://api.icme.io/mcp
protocol
streamable-http ·2025-03-26
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is icme-preflight live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is icme-preflight free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does icme-preflight have?
14 tools: create_account_card, top_up, top_up_card, poll_session, verify_proof, run_tests, make_rules, create_account, ….
Is icme-preflight safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.6%

90 days 98.8%· all time 98.8%

latency
472ms

last good check

priced tools
0

of 14 tools

_ answered our checks, 90 days 514 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
security & compliance prompt & content safety
used for
  • verify an agent action against a policy
  • turn a plain-english policy into a guardrail
  • check reasoning for contradictions
  • run policy test cases
  • verify a zero-knowledge proof of a check
takes → gives
text → data
tools
9 reads3 changes data2 moves money
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 3 doors on this origin, so the chain figures are the operator's. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
0

distinct

settlements
0

none in the window

received on chain
0 USDC

thin

_ what it can do 14 tools
2 open4 auth-required 8 never probed 6 of 14 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • check_action_paid reads open 20h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "policy_id",
    "action"
  ],
  "properties": {
    "action": {
      "type": "string",
      "description": "The agent action to verify against the policy (max 2000 chars)"
    },
    "policy_id": {
      "type": "string",
      "format": "uuid",
      "description": "Policy ID from make_rules"
    }
  }
}
    arguments 18 lines
  • check_logic reads open 20h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "reasoning"
  ],
  "properties": {
    "show_smt": {
      "type": "boolean",
      "description": "Include the generated SMT-LIB2 formula in the response for inspection (default: false)"
    },
    "reasoning": {
      "type": "string",
      "description": "The reasoning, plan, or chain of thought to check. Be specific — include numbers, conditions, and constraints for the best results (max 2000 chars)"
    }
  }
}
    arguments 16 lines
  • quick_check reads auth-required 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "policy_id",
    "action",
    "api_key"
  ],
  "properties": {
    "action": {
      "type": "string",
      "description": "The agent action to check (max 2000 chars)"
    },
    "api_key": {
      "type": "string",
      "description": "Your ICME API key"
    },
    "policy_id": {
      "type": "string",
      "format": "uuid",
      "description": "Policy ID from make_rules"
    }
  }
}
    arguments 23 lines
  • check_action reads auth-required 20h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "policy_id",
    "action",
    "api_key"
  ],
  "properties": {
    "action": {
      "type": "string",
      "description": "The agent action to verify against the policy (max 2000 chars)"
    },
    "api_key": {
      "type": "string",
      "description": "Your ICME API key"
    },
    "policy_id": {
      "type": "string",
      "format": "uuid",
      "description": "Policy ID from make_rules"
    }
  }
}
    arguments 23 lines
  • check_relevance reads auth-required 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "policy_id",
    "action",
    "api_key"
  ],
  "properties": {
    "action": {
      "type": "string",
      "description": "The agent action to screen (max 2000 chars)"
    },
    "api_key": {
      "type": "string",
      "description": "Your ICME API key"
    },
    "policy_id": {
      "type": "string",
      "format": "uuid",
      "description": "Policy ID from make_rules"
    },
    "threshold": {
      "type": "number",
      "description": "Relevance threshold (0.0 to 1.0). Default 0.0 — any match triggers should_check. Optional."
    }
  }
}
    arguments 27 lines
  • get_scenarios reads auth-required 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "policy_id",
    "api_key"
  ],
  "properties": {
    "api_key": {
      "type": "string",
      "description": "Your ICME API key"
    },
    "policy_id": {
      "type": "string",
      "format": "uuid",
      "description": "Policy ID from make_rules"
    }
  }
}
    arguments 18 lines
  • create_account_card changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "username"
  ],
  "properties": {
    "username": {
      "type": "string",
      "description": "Unique username (1-32 chars, alphanumeric + hyphens/underscores)"
    }
  }
}
    arguments 12 lines
  • top_up moves money unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "api_key"
  ],
  "properties": {
    "api_key": {
      "type": "string",
      "description": "Your ICME API key"
    }
  }
}
    arguments 12 lines
  • top_up_card changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "amount_usd",
    "api_key"
  ],
  "properties": {
    "api_key": {
      "type": "string",
      "description": "Your ICME API key"
    },
    "amount_usd": {
      "type": "integer",
      "description": "Top-up amount in USD: 5, 10, 25, 50, or 100"
    }
  }
}
    arguments 17 lines
  • poll_session reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "session_id"
  ],
  "properties": {
    "session_id": {
      "type": "string",
      "description": "The session_id returned by create_account_card or top_up_card"
    }
  }
}
    arguments 12 lines
  • verify_proof reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "proof_id"
  ],
  "properties": {
    "proof_id": {
      "type": "string",
      "format": "uuid",
      "description": "The proof_id returned by a prior check_action or check_action_paid call"
    }
  }
}
    arguments 13 lines
  • run_tests reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "policy_id",
    "api_key"
  ],
  "properties": {
    "api_key": {
      "type": "string",
      "description": "Your ICME API key"
    },
    "policy_id": {
      "type": "string",
      "format": "uuid",
      "description": "Policy ID to test"
    }
  }
}
    arguments 18 lines
  • make_rules changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "policy",
    "api_key"
  ],
  "properties": {
    "policy": {
      "type": "string",
      "description": "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": {
      "type": "string",
      "description": "Your ICME API key (from create_account or create_account_card)"
    }
  }
}
    arguments 17 lines
  • create_account moves money unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "username"
  ],
  "properties": {
    "username": {
      "type": "string",
      "pattern": "^[a-zA-Z0-9_-]{1,32}$",
      "description": "Unique username (1-32 chars, alphanumeric + hyphens/underscores)"
    }
  }
}
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b69b381f1b3f624e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b69b381f1b3f624e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b69b381f1b3f624e/badge.svg)](https://brick.blue/agent/b69b381f1b3f624e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.