# io.github.LedgerProof/laen (remote · jmspfggpztykyubyzvlx.supabase.co)

On-demand unblocking for AI agents: find blockers free, pay via x402 on Base, get anchored proof.

- Trust score: 63/100 (medium)
- Change this week: +3
- Registry status: deprecated
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

> **Deprecated**: this server is marked deprecated in the MCP registry.

## Components

- remote · `jmspfggpztykyubyzvlx.supabase.co`: 63/100 (this document), [markdown](https://verifymcp.io/servers/ledgerproof-laen/functions-v1-laen-mcp.md), [page](https://verifymcp.io/servers/ledgerproof-laen/functions-v1-laen-mcp)

## Channel facts

- Endpoint: `https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 617 tokens (~205/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ledgerproof-laen https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp
```

### Codex

```toml
[mcp_servers.ledgerproof-laen]
url = "https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ledgerproof-laen": {
      "type": "remote",
      "url": "https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ledgerproof-laen --url https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ledgerproof-laen:
    url: "https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 62, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 60, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 59)

First indexed and scored.

## MCP tools (3)

### `laen_find_blockers` (~161 tokens)

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.

Input parameters:

- `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)

### `laen_quote` (~112 tokens)

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.

Input parameters:

- `blocker_id` (string, required): the blocker/obligation id (obl_<16hex>)
- `product` (string): receipt $0.25 (evidence) | certificate $0.50 (evidence + fresh anchored receipt w/ verify_url)

### `laen_resolve` (~143 tokens)

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.

Input parameters:

- `blocker_id` (string, required): 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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ledgerproof-laen/functions-v1-laen-mcp#diagnostics

## Score history

- 2026-08-03: 63
- 2026-08-02: 63
- 2026-08-01: 62
- 2026-07-31: 62
- 2026-07-30: 60
- 2026-07-29: 61
- 2026-07-28: 61
- 2026-07-27: 60
- 2026-07-26: 59

## Links

- Remote endpoint: https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp
- Website: https://ledgerproofhq.io/
- Changelog RSS feed: https://verifymcp.io/servers/ledgerproof-laen/functions-v1-laen-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ledgerproof-laen/functions-v1-laen-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ledgerproof-laen/functions-v1-laen-mcp