mcpbeat Sign in

Lumen Pre-Sign Check MCP Server

not responding

Lumen Pre-Sign Check is listed as active in the registry but did not answer our last check. It exposes 2 tools. Last commit 11 Oct 2026.

Use before signing an EVM tx or EIP-712 message: risk flags + verdict. Informational, no simulation

Uptime history 29 days of history · worst day 0%
29 days agonow
0.0%
Uptime 24h
0 of 92 checks
2
Tools
read from the server
201 ms
Response time
average over 24h
0
Stars
last commit 11 Oct 2026

Lumen Pre-Sign Check does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add lumen-presign-check --transport http https://lumenworks-x402-decoder.onrender.com/mcp/presign
Settings → Connectors → Add custom connector, then paste this address
https://lumenworks-x402-decoder.onrender.com/mcp/presign
~/.codex/config.toml
[mcp_servers.lumen-presign-check]
url = "https://lumenworks-x402-decoder.onrender.com/mcp/presign"
.cursor/mcp.json
{
  "mcpServers": {
    "lumen-presign-check": {
      "url": "https://lumenworks-x402-decoder.onrender.com/mcp/presign"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "lumen-presign-check": {
      "type": "http",
      "url": "https://lumenworks-x402-decoder.onrender.com/mcp/presign"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

explain
explain_before_sign
Lumen Pre-Sign Check. Use before signing any EVM transaction or EIP-712 message: returns {summary, flags[], verdict} with verdict looks_ok | review | do_not_sign_unless_intended. Flags unlimited approve/increaseAllowance, EIP-2612 Permit and Permit2 (typed data and on-chain), setApprovalForAll, unknown spender, admin calls (upgradeTo/transferOwnership), zero-price Seaport orders, long deadlines, chain mismatch and x402 payTo mismatch; decodes multicall/aggregate3 inner calls one level. Example: USDC approve(spender, 2^256-1) -> do_not_sign_unless_intended, UNLIMITED_APPROVAL. Agent policy: abort on do_not_sign_unless_intended, escalate review. Informational, not a security guarantee; looks_ok does not mean safe; no simulation. $0.002, no signup, free tier 20/h; not charged if the call errors.
x402
x402_payment_safety_check
FREE, deterministic pre-payment check for an x402 endpoint. Give {url} (we fetch its unpaid 402) and/or {payment_required} (402 JSON or base64 header), plus optional expected_pay_to, expected_network, max_price_usdc, listed_price_usdc, facilitator_url, client_config {max_per_call_usdc, max_daily_usdc, idempotency_key, allow_any_pay_to}. Returns verdict ok/review/do_not_pay with checks: HTTPS/health, payTo validity & mismatch, unknown asset/network, price sanity vs cap/listing, timeout/replay window, multiple payTo, unknown facilitator, missing spend caps/idempotency. Nothing is stored; inputs that look like private keys are rejected.

Endpoints

URLTransportStateLatencyChecked
https://lumenworks-x402-decoder.onrender.com/mcp/presign streamable-http answering 201 ms 0 min ago

Alternatives to Lumen Pre-Sign Check

same job, measured the same way
Ethereum & EVM Message Signing
by nirholas

Sign Ethereum messages - EIP-191, EIP-712 typed data, Permit2, signature verification and recovery

104 installs/wk local only
Verdix address risk
by verdixapi

Check an EVM address on Base before sending funds: safe/caution/danger. Pays per call via x402.

322 installs/wk local only
Wren Pre-sign Check
by claudeisgod

Check a tx, EIP-712 payload, text or Base token before your agent signs. Paid per call over x402.

4 tools answering
Payment Guard MCP
by mlawsonking

Pre-send risk check for AI agents that move money — screen an address or payment URL before sending.

74 installs/wk local only
Resume-effect reconciliation for checkpointed agent runs
by textforagents

Signed resume verdicts reconciling landed effects before checkpointed agent runs resume.

answering
Deadchannel
by plus8bit

Check an x402 endpoint before you pay it: verdict, risk score and what is wrong. $0.005 in USDC.

51 installs/wk local only
Lumi Verdict: check an x402 seller before paying
by cypher-osiris

One signed label before paying an x402 seller, from Lumi's test-buys on XRPL, Base and Stellar

77 installs/wk local only
Base Tx Preflight
by madebydevx-preflight

Simulate a Base tx before signing: revert reason, gas limit, full fee in ETH/USD. Paid x402.

2 tools answering

Lumen Pre-Sign Check — questions

Answers built from our own checks of this server.

What can Lumen Pre-Sign Check do?
It exposes 2 tools, read directly from the server on our last check. Among them: explain_before_sign, x402_payment_safety_check. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Lumen Pre-Sign Check working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 201 ms. The bar chart above shows every period we have measured.
The registry lists Lumen Pre-Sign Check as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Lumen Pre-Sign Check?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Lumen Pre-Sign Check need an API key?
No. Lumen Pre-Sign Check completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
Is Lumen Pre-Sign Check open source?
The code is open source: it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 2 open issues. The licence covers the code in the repository, not the hosted service at lumenworks-x402-decoder.onrender.com, which runs on its operator's own terms.