mcp server
laen
On-demand unblocking for AI agents: find blockers free, pay via x402 on Base, get anchored proof.
Description as published by the maintainer. Source
- version 1.0.0
- archived
archived — Registry status is "deprecated".
What this server can do
3 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
laen_find_blockers(limit, subject, gap_type, identifier, obligation_class)- FREE. Search LAEN's live blocker feed (universal blocker schema) for execution blockers matching a failure signature. Returns fundable blockers with gap_type, failing_assertion, resolution_contract (x402), resolution_state (KNOWN_RESOLUTION = instant), and measured latency where available.
laen_quote(product, blocker_id)- FREE. Get the price and EXACT x402 payment requirements for resolving one blocker. Use the returned requirements.accepts[0] to construct/sign your payment with your own x402 client (e.g. x402-fetch createPaymentHeader). Never share keys. Required: blocker_id.
laen_resolve(product, x_payment, blocker_id)- PAID (your wallet). Submit your SIGNED x402 payment payload (the base64 X-PAYMENT header value your client produced for this blocker's requirements) and receive the resolution: independently verifiable evidence (+ anchored certificate with verify_url if product=certificate). Fail-closed: no valid settled payment, no evidence. Without x_payment this returns the 402 requirements so you can pay and retry. Required: blocker_id.
Last successful function declaration observed on . Source: https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-01 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-24 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 3 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | jmspfggpztykyubyzvlx.supabase.co | |
| mcp endpoint status | ok | The server listed 3 functions when asked. | as of probe | jmspfggpztykyubyzvlx.supabase.co |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json