MCP server de Lumen Agent Utilities
Commit 11 oct 2026Permite que los agentes de IA decodifiquen transacciones de EVM, obtengan contenido web en formato Markdown, realicen búsquedas de DNS y consulten bases de datos académicas o financieras.
También conocido como Dansgit2b/lumenworks-x402-api, lumenworks-decoder
- Stars
- 0
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- 1.4.0
- Último commit
- 11 oct 2026
- Licencia
- MIT
¿Qué es Lumen Agent Utilities MCP?
Lumen Agent Utilities es un MCP server. Permite que los agentes de IA decodifiquen transacciones de EVM, obtengan contenido web en formato Markdown, realicen búsquedas de DNS y consulten bases de datos académicas o financieras.
Resumen generado a partir del README del proyecto
Acerca del MCP server de Lumen Agent Utilities
Lumen Agent Utilities proporciona un conjunto de herramientas especializadas diseñadas para que los agentes de IA interactúen con datos de blockchain, web y académicos. Los desarrolladores pueden conectarse a este MCP server remoto vía HTTP para acceder a funciones como la decodificación de calldata de EVM, la realización de búsquedas de DNS y la obtención de contenido web en Markdown limpio. El servidor opera bajo un modelo de pago por uso mediante el protocolo x402, con costos que oscilan entre 0.001 y 0.002 USDC por solicitud, aunque un nivel gratuito permite 20 llamadas por hora por dirección IP.
Los usuarios pueden utilizar herramientas específicas como eip712_decode para analizar datos tipados, evm_address_lookup para consultar saldos y registros de ENS, y pubmed_search o arxiv_search para investigación académica. El sistema admite liquidaciones en la mainnet de Base y puede integrarse con Celo si se proporciona una API key específica. Está diseñado para desarrolladores que crean agentes autónomos que requieren datos verificables de la web, registros financieros a través de SEC EDGAR o detalles técnicos de blockchain sin necesidad de gestionar entornos locales complejos.
Qué puedes hacer con él
- 1Convertir páginas web a textoUn desarrollador puede instruir a una IA para que extraiga el contenido de una URL y reciba la información en un formato Markdown estructurado para facilitar su procesamiento.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar Lumen Agent Utilities MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar Lumen Agent Utilities MCP en Claude Code
$ claude mcp add --transport http lumenworks-decoder https://lumenworks-x402-decoder.onrender.com/mcpInstalar Lumen Agent Utilities MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"lumenworks-decoder": {
"url": "https://lumenworks-x402-decoder.onrender.com/mcp"
}
}
}Instalar Lumen Agent Utilities MCP en VS Code
.vscode/mcp.json
{
"servers": {
"lumenworks-decoder": {
"type": "http",
"url": "https://lumenworks-x402-decoder.onrender.com/mcp"
}
}
}Instalar Lumen Agent Utilities MCP en VS Code CLI
$ code --add-mcp '{"name":"lumenworks-decoder","type":"http","url":"https://lumenworks-x402-decoder.onrender.com/mcp"}'Instalar Lumen Agent Utilities MCP en Codex
$ codex mcp add lumenworks-decoder --url https://lumenworks-x402-decoder.onrender.com/mcpInstalar Lumen Agent Utilities MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.lumenworks-decoder] url = "https://lumenworks-x402-decoder.onrender.com/mcp"
Instalar Lumen Agent Utilities MCP en Gemini CLI
$ gemini mcp add -s user --transport http lumenworks-decoder https://lumenworks-x402-decoder.onrender.com/mcpInstalar Lumen Agent Utilities MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"lumenworks-decoder": {
"url": "https://lumenworks-x402-decoder.onrender.com/mcp",
"type": "http"
}
}
}README
Ver en GitHubLumen Works Agent API (x402)
Two listings on one origin:
- Lumen Pre-Sign Check:
POST /v1/tx/explain($0.002). Use before signing any EVM transaction or EIP-712 message; returns{summary[], flags[], verdict}withlooks_ok | review | do_not_sign_unless_intended. Agent policy: abort ondo_not_sign_unless_intended, escalatereview. Informational, not a security guarantee; looks_ok does not mean safe; no simulation. Accuracy set and known limits: ACCURACY.md. MCP:/mcp/presign. - Lumen Agent Utilities: every other route below. MCP:
/mcp.
Trust terms: no signup; free tier 20 calls/hour/IP under /v1/free/...; GET/HEAD on any paid path returns the 402 quote (it never settles); not charged when a call errors, because the x402 middleware settles only after the handler returns a status below 400. Input schemas and real example outputs (examples.json, captured live by test/capture-examples.mjs) are in each route's Bazaar extension and in /openapi.json, validated with node test/validate-bazaar.mjs <base>.
Stats: /v1/stats has anonymous aggregates only (UA family, daily unique counts from salted daily-rotating IP hashes, 30-day retention). They persist across deploys when STATS_GIST_ID + STATS_GIST_TOKEN (a gist-only token) are set; otherwise they are kept in memory.
Pay-per-call agent utilities, 0.001–0.002 USDC per call on Base mainnet via x402 (exact scheme, PayAI public facilitator). Author: Dan (Dansgit2b). Early-stage, unaudited.
| Endpoint (POST JSON) | What |
|---|---|
/v1/x402/lint {header} |
decode + lint x402 PAYMENT-REQUIRED/SIGNATURE/RESPONSE |
/v1/eip712/decode {typedData} |
domain separator, digest, risk notes |
/v1/calldata/decode {data, signature?} |
selector, openchain/4byte lookup, decoded args |
/v1/web/markdown {url, fullPage?, maxChars?} — $0.001 |
public page → clean Markdown (Readability) + metadata. No JS rendering. |
/v1/web/unfurl {url} — $0.001 |
final URL, status, title, description, OG image, canonical, favicon |
/v1/evm/address {address} (0x or ENS) — $0.002 |
Ethereum+Base: ENS + records, EOA/contract/7702, balances, USDC/USDT, ERC-20 info (public RPC) |
/v1/domain/lookup {domain} — $0.002 |
DNS (DoH) A/AAAA/MX/NS/TXT/CAA, SPF/DMARC, RDAP registrar/created/expiry, age |
Free tier: same paths under /v1/free/... (20/hour/IP). Discovery: /, /.well-known/x402, /openapi.json, /llms.txt.
payTo: 0xee9790cB3960952F585379F831a89b4e00B4029A.
End-to-end proof (local run, 2026-10-10): paid call settled on Base, tx 0xff4af45df7caeef958b77700e96ba94e5ed37d3bac6e8cf40d6528a9497d77d4.
Deploy: Render (render.yaml, free plan) or any Docker host (Dockerfile). Set PUBLIC_BASE to the public origin. No secrets needed (server only receives payments). License MIT.
MCP server
Remote MCP (streamable HTTP, stateless JSON): https://lumenworks-x402-decoder.onrender.com/mcp, with tools x402_lint, eip712_decode, calldata_decode, web_markdown, url_unfurl, evm_address_lookup and domain_lookup. Free tier: 20 tool calls/hour/IP. After that the tool returns the x402 payment requirements for the matching paid HTTP endpoint (0.001–0.002 USD).
Celo
When X402_CELO_API_KEY (from the x402.celo.org dashboard) is set, every paid route also accepts USA₮ and USDC on Celo (eip155:42220), settled through Celo's hosted facilitator at api.x402.celo.org.
Free x402 payment safety check
POST /v1/x402/safety-check (MCP tool x402_payment_safety_check) — deterministic pre-payment check. Body: {url?, method?, payment_required?, expected_pay_to?, expected_network?, max_price_usdc?, listed_price_usdc?, facilitator_url?, client_config?}. We fetch the unpaid 402 (SSRF-guarded) and return ok | review | do_not_pay with checks: HTTPS/health/latency, payTo validity/checksum/mismatch, unknown asset/network, price vs your cap and the listed price, timeout/replay window, multiple payTo, unknown facilitator, missing spend caps / idempotency in your client config. Nothing is stored; inputs that look like private keys are rejected. 30/hour/IP.
Planned (not built): continuous monitoring with alerts on price/payTo/asset changes. Free waitlist: POST /v1/monitoring/waitlist {endpoint_url, contact?} (5/hour/IP). No date promised; stored in memory/logs only on a free host, so it may be lost on restart.
Stats
GET /v1/stats — anonymous in-memory counters since last restart: calls per endpoint, unpaid 402s vs paid settlements (conversion), coarse user-agent buckets. No IPs or bodies stored.
v1.3: explain-before-you-sign + public-data tools
| Endpoint (POST) | Price | MCP tool | Upstream (free, no key) |
|---|---|---|---|
/v1/tx/explain |
0.002 | explain_before_sign |
calldata (openchain/4byte) + EIP-712, risk flags |
/v1/pubmed/search |
0.001 | pubmed_search |
NCBI E-utilities |
/v1/arxiv/search |
0.001 | arxiv_search |
arXiv API |
/v1/sec/filings |
0.001 | sec_filings |
SEC EDGAR (set SEC_USER_AGENT with a contact email per SEC policy) |
/v1/weather/forecast |
0.001 | weather_forecast |
Open-Meteo (CC BY 4.0) |
/v1/polymarket/markets |
0.001 | polymarket_markets |
Polymarket Gamma (read-only data) |
Free tier: /v1/free/<path> or MCP, 20 calls/hour/IP.
Facilitators
If CDP_API_KEY_ID and CDP_API_KEY_SECRET are set, Coinbase's CDP facilitator is used first. Settlements through it are what get the service indexed in the x402 Bazaar. The PayAI facilitator stays registered as the fallback. Without CDP keys, PayAI handles everything, as before.
Preguntas sobre Lumen Agent Utilities MCP
¿Cómo agrego Lumen Agent Utilities MCP a Claude Code?
Ejecuta claude mcp add --transport http lumenworks-decoder https://lumenworks-x402-decoder.onrender.com/mcp en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego Lumen Agent Utilities MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Puedo usar esto para verificar si una transacción de EVM es segura para firmar?
Sí, el Lumen Pre-Sign Check devuelve un resumen y un veredicto para ayudarte a decidir si debes firmar una transacción o un mensaje EIP-712.
¿Cómo se gestionan los pagos de las rutas de pago?
Los pagos se gestionan a través del protocolo x402 en la mainnet de Base, con un costo de entre 0.001 y 0.002 USDC por llamada.