io.github.LedgerProof/laen
REMOTE · JMSPFGGPZTYKYUBYZVLX.SUPABASE.CO · SCANNED AUG 3
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.
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 →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · jmspfggpztykyubyzvlx.supabase.co
claude mcp add --transport http ledgerproof-laen 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": {
"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.
- 2 Aug 26 +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.
- 31 Jul 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
- 30 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 59
First indexed and scored.
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 3 Aug 2026 · Probed https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=supabase.co | CN=WE1,O=Google Trust Services,C=US | 28 Jun 2026 | 26 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | 1d2d53f65d874dfb0eead7aab0301afd |
| SANs: supabase.co, *.supabase.co | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of jmspfggpztykyubyzvlx.supabase.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| supabase.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp | Verified | 200 | |
| http (plaintext) | http://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp | HTTPS enforced | 301 | https://jmspfggpztykyubyzvlx.supabase.co/functions/v1/laen-mcp |
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.
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.