io.github.LedgerProof/laen
REMOTE · JMSPFGGPZTYKYUBYZVLX.SUPABASE.CO · SCANNED SEP 13
On-demand unblocking for AI agents: find blockers free, pay via x402 on Base, get anchored proof.
Available components
Deprecated
This server is marked deprecated in the MCP registry.
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the io.github.LedgerProof/laen MCP server?
io.github.LedgerProof/laen is a hosted endpoint at https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · jmspfggpztykyubyzvlx.supabase.co
claude mcp add --transport http ledgerproof-laen 'https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp'
{
"mcpServers": {
"ledgerproof-laen": {
"url": "https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp"
}
}
} {
"servers": {
"ledgerproof-laen": {
"type": "http",
"url": "https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp"
}
}
} [mcp_servers.ledgerproof-laen] url = "https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ledgerproof-laen": {
"type": "remote",
"url": "https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp",
"enabled": true
}
}
} openclaw mcp add ledgerproof-laen --url 'https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp' --transport streamable-http
mcp_servers:
ledgerproof-laen:
url: "https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp" {
"McpServers": {
"ledgerproof-laen": {
"Transport": "http",
"Url": "https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp"
}
}
} assistant mcp add ledgerproof-laen -t streamable-http -u 'https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp'
{
"mcpServers": {
"ledgerproof-laen": {
"type": "http",
"url": "https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 13 Sept 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 12 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 11 Sept 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 10 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 9 Sept 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 7 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 13 Sept 2026 · Probed https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of jmspfggpztykyubyzvlx.supabase.co. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| jmspfggpztykyubyzvlx.supabase.co. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp | Unreachable | ||
| http (plaintext) | http://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
army_buy ~171
PAID (your wallet). Submit the signed X-PAYMENT payload your client produced for this service's requirements and receive the deliverable plus a FREE cryptographic hash receipt with an independently checkable verify_url. Fail-closed and proof-gated: if the deliverable does not pass its published acceptance rule, the response is an error and YOUR AUTHORIZATION IS NEVER CAPTURED — you are not charged for work that failed its own test. Without x_payment this returns the 402 requirements so you can pay and retry.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | – | the request body for the service |
| service_id | string | yes | soldier id, e.g. sol-01-web-search |
| x_payment | string | – | base64 X-PAYMENT payload signed by YOUR wallet for this service's x402 requirements |
No output schema declared.
No examples provided.
army_list_services ~236
FREE. List the LedgerProof Settlement Army's 21 live data services an agent can buy per-call with x402 (USDC on Base, no account, no subscription, no signup). Each entry returns its price in USD, the exact resource URL to call, and the PUBLISHED ACCEPTANCE RULE that must hold before payment is captured — settlement is proof-gated, so a deliverable that fails its own test is never charged for. Covers live web search and page extraction, prediction-market odds priced across Polymarket AND Kalshi with the cross-venue spread, FX and technical indicators, SEC filings, FDA recalls, CVE lookups, sanctions screening, DNS/RDAP, GLEIF LEI, Wikidata, Federal Register, World Bank indicators, weather, GitHub repo facts, and hash anchoring/verification. Call this first to see what exists and what it costs.
| Name | Type | Req | Description |
|---|---|---|---|
| max_price_usd | number | – | optional: only return services at or below this price |
| query | string | – | optional substring filter over service id and description (e.g. 'prediction', 'search', 'sanctions') |
No output schema declared.
No examples provided.
army_quote ~137
FREE. Get the EXACT x402 payment requirements for one Settlement Army service, for the specific input you intend to buy. Returns the verbatim 402 challenge — use requirements.accepts[0] to construct and sign a payment with your OWN x402 client and wallet (e.g. x402-fetch createPaymentHeader). Never send keys anywhere; this server never holds funds and never signs.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | – | the request body you intend to buy, e.g. {"mode":"prediction","query":"election"} |
| service_id | string | yes | soldier id from army_list_services, e.g. sol-23-onchain-base |
No output schema declared.
No examples provided.
laen_find_blockers ~161
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.
| Name | Type | Req | Description |
|---|---|---|---|
| gap_type | string | – | e.g. provenance_chain_break, unverified_safety_recall |
| identifier | string | – | identifier/URL substring to match (e.g. api.example.com) |
| limit | number | – | max results (default 10) |
| obligation_class | string | – | safety | ai_governance | regulatory | ... |
| subject | string | – | subject/entity name to match (e.g. a vendor, product, or host) |
No output schema declared.
No examples provided.
laen_quote ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| blocker_id | string | yes | the blocker/obligation id (obl_<16hex>) |
| product | string | – | receipt $0.25 (evidence) | certificate $0.50 (evidence + fresh anchored receipt w/ verify_url) |
No output schema declared.
No examples provided.
laen_resolve ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| blocker_id | string | yes | the blocker/obligation id (obl_<16hex>) |
| product | string | – | – |
| x_payment | string | – | base64 X-PAYMENT payload signed by YOUR wallet for this blocker's x402 requirements |
No output schema declared.
No examples provided.
What is the io.github.LedgerProof/laen MCP server?
io.github.LedgerProof/laen is an MCP server listed in the public MCP registry as io.github.LedgerProof/laen. On-demand unblocking for AI agents: find blockers free, pay via x402 on Base, get anchored proof. This page covers its hosted endpoint (https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp).
Is the io.github.LedgerProof/laen MCP server safe to use?
io.github.LedgerProof/laen scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.LedgerProof/laen MCP server expose?
io.github.LedgerProof/laen exposes 6 tools: laen_find_blockers, laen_quote, laen_resolve, army_list_services, army_quote, army_buy. Their descriptions and schemas cost roughly 960 tokens of context every time the server is loaded.
Does the io.github.LedgerProof/laen MCP server require authentication?
Its publisher declares no required credentials for io.github.LedgerProof/laen. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.LedgerProof/laen MCP server still maintained?
io.github.LedgerProof/laen is marked deprecated in the MCP registry. We last reached this channel on 6 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.