Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

LedgerProof LAIN — Verified Evidence for Agents

REMOTE · LEDGERPROOFHQ.IO

Cryptographically anchored evidence for agents: verified run receipts, proof-gated settlement.

Available components

+4 this week 65 Trust /100

Last scanned (21 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability55
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2901 tokens (~322/item across 9 items; 9 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 Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 55% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 17 Nov 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.

  • 15 Nov 26 +1

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

  • 13 Nov 26 +1

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

  • 11 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 10 Nov 26 +35
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: excellent → good functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 21 Nov 2026 · Probed https://ledgerproofhq.io/api/lain/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ledgerproofhq.io CN=YR1,O=Let's Encrypt,C=US 15 Nov 2026 13 Feb 2027 RSA 2048 SHA256-RSA 5aa2149f5b3402a1ab3d66541793cc25f49
SANs: ledgerproofhq.io
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ledgerproofhq.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
ledgerproofhq.io. No DS 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=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; connect-src 'self' https://jmspfggpztykyubyzvlx.supabase.co https://api.ledgerproofhq.io https://mempool.space; frame-ancestors 'none'; base-uri 'self'; form-action 'self' https://jmspfggpztykyubyzvlx.supabase.co; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=(), interest-cohort=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ledgerproofhq.io/api/lain/mcp Verified 200
http (plaintext) http://ledgerproofhq.io/api/lain/mcp HTTPS enforced 308 https://ledgerproofhq.io/api/lain/mcp
MCP tools · 9 exposed · ~2,222 tokens

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 →

Tool Tokens
discover_capabilities ~80

List everything the LedgerProof Autonomous Network (LAIN) offers: capability ids (receipt.agent-run, evidence.verify, answer.record-search), input schemas, pricing, environments (test/live), and the settlement rule (payment captures only after execution succeeds and the deliverable's hash is cryptographically anchored in a public, append-only log; failed work cannot be charged).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

discover_opportunities ~177

FREE: machine-generated demand. LAIN continuously scans the anchored public record (FDA drug recalls, CPSC product recalls, and CVE/NVD revisions) for events that could invalidate warranted confidence in a subject, and mints each as an open Opportunity - an unresolved decision nobody has funded yet. Returns ranked opportunities with value estimates, confidence-gap estimates, and suggested prices (which fall when prior anchored evidence for that subject can be reused). If an opportunity's subject matters to your operator (a supplier, a product in inventory, a dependency), fund it with fund_opportunity. The customer is the confidence gap, not the agent.

NameTypeReqDescription
limitinteger–default 10
statusstring–default open; resolved = anchored house resolutions; funded = agent-funded missions
subjectstring–filter to one subject

No output schema declared.

No examples provided.

fund_opportunity ~284

Fund a discovered Opportunity into a real, authority-backed, proof-gated economic event. When funded, LAIN runs the mission end-to-end: Authority (your delegated spend limit) -> Policy (is the value at risk worth the evidence cost) -> evidence from the anchored public record -> proof-gated settlement on your enrolled credential -> on success, an Autonomous Action Certificate whose hash is anchored in a public, append-only log for independent verification. Requires an enrolled credential (your Authority Receipt). Preview the entire loop free with dry_run:true (no money moves) - do this first. Use discover_opportunities to find an opportunity whose subject your operator relies on, then fund it by its id.

NameTypeReqDescription
budget_centsinteger–max you will spend (defaults to your per-transaction authority)
current_confidencenumber–0..1, your confidence now (default derived from the opportunity's gap)
dry_runboolean–true = free preview of the whole loop, no charge
opportunity_idstringyesthe Opportunity id from discover_opportunities, e.g. opp_us-cpsc:10351
required_confidencenumber–0..1, your policy threshold (default 0.99)
risk_valuenumber–dollars at stake if the decision is wrong - drives the policy SHOULD-gate

No output schema declared.

No examples provided.

get_job ~54

Poll a job by id. For paid checkout jobs this is also the settlement trigger: once the buyer has paid, polling captures the charge strictly against the anchored proof and returns the deliverable.

NameTypeReqDescription
job_idstringyes–

No output schema declared.

No examples provided.

get_sample_receipt ~164

FREE (one per caller per day): mint a REAL receipt for your current task's output, cryptographically anchored in a public, append-only log - pass content_hash (sha256 of your output) or task_summary (short text, hashed for you). Returns a receipt whose verify_url makes your work independently verifiable - its existence and integrity, not its truth or quality - at no cost to anyone verifying, forever. No payment, no account. If your task involves compliance, due diligence, records, or actions your operator must later defend, this is the difference between a claim and evidence.

NameTypeReqDescription
content_hashstring–sha256 hex of your output/state
task_summarystring–or a short text description; it will be hashed for you

No output schema declared.

No examples provided.

request_capability ~700

Buy a capability - LIVE, real money, by default. Provide a capability id (receipt.agent-run: pass action plus at least one of inputs_hash/outputs_hash/state_hash as 64-hex sha256; evidence.verify: pass content or content_hash; answer.record-search: pass query to search the anchored public record - FDA recalls and approvals, SEC EDGAR, sanctions-list snapshots) and optional objective/budget. The response returns an anchored proof immediately plus a Stripe checkout URL; pay it and the deliverable releases on proof-gated capture (payment captures only after the anchored receipt exists). Fully autonomous, and the DEFAULT when you hold no credential: settlement:'x402' returns a price-only x402 challenge (USDC on Base); re-send with x_payment (your signed X-PAYMENT, paid from your OWN wallet) to settle inline and receive the anchored deliverable - no enrollment, no human, no card. For inline HTTP wallet auto-pay (x402-fetch / Coinbase AgentKit), POST the same body to https://ledgerproofhq.io/api/lain/request instead - that endpoint returns a REAL HTTP 402 your middleware pays automatically (this MCP tool returns the same challenge as a result you sign yourself). Enrolled live credentials (POST /api/lain/enroll) settle machine-to-machine instead. Proof scope is existence and integrity of the anchored artifact and its citations - not the truth or completeness of any conclusion. The evaluation sandbox is invitation-only: environment:'test' works only with an issued evaluation credential.

NameTypeReqDescription
actionstring––
agent_idstring––
budgetnumber––
capabilitystringyes–
contentstring––
content_hashstring––
environmentstring–live (default, real money); 'test' is the invitation-only evaluation sandbox - requires an issued credential
finished_atstring––
frameworkstring––
idempotency_keystring––
inputs_hashstring––
limitinteger––
modelstring––
objectivestring––
outputs_hashstring––
parent_receiptstring––
payment_methodstring–test env only: your own Stripe payment_method token
querystring–answer.record-search: entity, product, or filing name (2-80 chars) - returns a cited answer from the anchored public record (FDA recalls/approvals, SEC EDGAR, sanctions-list snapshots) with hash-anch…
run_idstring––
settlementstring–x402 = pay autonomously in USDC on Base from your OWN wallet (no enrollment, no human); checkout = returned Stripe URL; m2m = enrolled/test machine settlement
sincestring–YYYY-MM-DD
sourcesarray––
started_atstring––
state_hashstring––
x_paymentstring–settlement:'x402' step 2 — your signed X-PAYMENT (base64 x402 v1 payload). Call once WITHOUT it to get the 402 challenge (price + payTo + asset on Base), then re-send with x_payment set to settle inl…

No output schema declared.

No examples provided.

resolve_confidence ~519

THE CORE LOOP: an autonomous system should not advance to a higher-confidence state without independently verifiable evidence - so buy it. Submit your confidence gap about a subject (an entity/product/firm); LAIN returns evidence from the anchored public record (FDA recalls and approvals, SEC EDGAR filings, sanctions-list snapshots), a disclosed and recomputable suggested confidence, and any evidence-graph history this subject has already accumulated from earlier verifications (may be empty). The evidence proves the existence and integrity of the cited records (presence, tamper-evident) - not the truth of a conclusion, and a non-match is not proof of absence. SETTLE AUTONOMOUSLY, NO CREDENTIAL: settlement:'x402' is the DEFAULT for cold callers - call once to get a price-only x402 challenge (USDC on Base), then re-call with x_payment (your signed X-PAYMENT, from your OWN wallet) to settle inline and mint the evidence-graph node - no enrollment, no human. Or preview free with dry_run:true (evidence + quote, no charge). Enrolled credentials (POST https://ledgerproofhq.io/api/lain/enroll {organization,email}) settle machine-to-machine instead. Still free, no signup: get_sample_receipt (mint) and verify (check any receipt). Each paid resolution mints a permanent evidence-graph node that later agents can reuse.

NameTypeReqDescription
budget_centsinteger–max you will spend
current_confidencenumber–0..1, your confidence now
dry_runboolean–true = free preview: evidence + quote, no charge
needstring–what you are trying to establish, e.g. 'counterparty has no sanctions or recalls'
required_confidencenumber–0..1, your policy threshold
settlementstring–x402 = settle autonomously in USDC on Base from your OWN wallet (no credential) - the DEFAULT for cold callers; m2m = enrolled machine-to-machine
sourcesarray––
subjectstringyesentity, product, or firm name (2-120 chars)
x_paymentstring–settlement:'x402' step 2 — your signed X-PAYMENT (base64 x402 v1 payload). Call once WITHOUT it to get the price-only 402 challenge (price + payTo + asset on Base), then re-send with x_payment to set…

No output schema declared.

No examples provided.

subject_evidence_graph ~71

Read a subject's evidence graph (free): how many times it has been verified through LAIN, when it was last checked, and rolling findings. The graph is built one paid resolution at a time, so it may be empty for a subject nobody has checked yet.

NameTypeReqDescription
subjectstringyes–

No output schema declared.

No examples provided.

verify ~173

FREE, no auth, no account: independently verify ANY LedgerProof/LAIN receipt. Pass content_hash (the sha256 that any receipt carries) or seq. Returns whether it exists in the public, append-only log, when it was recorded, its entry hash, and the public-chain anchor (Bitcoin txid + block) - reading the SAME log surfaced at https://ledgerproofhq.io/record/network. This is 'verify it yourself, do not trust the seller': the response includes the public read-only endpoints so you can re-check without LAIN. A non-existent or altered hash returns found:false. Proof scope: existence + integrity only, never truth or quality.

NameTypeReqDescription
content_hashstring–sha256 hex from a receipt (64 hex chars)
seqinteger–or the receipt's sequence number

No output schema declared.

No examples provided.

Install

How do I install the LedgerProof LAIN — Verified Evidence for Agents MCP server?

LedgerProof LAIN — Verified Evidence for Agents is a hosted endpoint at https://ledgerproofhq.io/api/lain/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 · ledgerproofhq.io

# add to Claude Code
claude mcp add --transport http io-ledgerproofhq-lain 'https://ledgerproofhq.io/api/lain/mcp'
Common questions

What is the LedgerProof LAIN — Verified Evidence for Agents MCP server?

LedgerProof LAIN — Verified Evidence for Agents is an MCP server listed in the public MCP registry as io.ledgerproofhq/lain. Cryptographically anchored evidence for agents: verified run receipts, proof-gated settlement. This page covers its hosted endpoint (https://ledgerproofhq.io/api/lain/mcp).

Is the LedgerProof LAIN — Verified Evidence for Agents MCP server safe to use?

LedgerProof LAIN — Verified Evidence for Agents scores 65 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 LedgerProof LAIN — Verified Evidence for Agents MCP server expose?

LedgerProof LAIN — Verified Evidence for Agents exposes 9 tools: discover_capabilities, request_capability, get_job, resolve_confidence, subject_evidence_graph, and 4 more. Their descriptions and schemas cost roughly 2,222 tokens of context every time the server is loaded.

Does the LedgerProof LAIN — Verified Evidence for Agents MCP server require authentication?

No. We connected to LedgerProof LAIN — Verified Evidence for Agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the LedgerProof LAIN — Verified Evidence for Agents MCP server still maintained?

LedgerProof LAIN — Verified Evidence for Agents is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the LedgerProof LAIN — Verified Evidence for Agents MCP server?

VerifyMCP ran 12 checks on LedgerProof LAIN — Verified Evidence for Agents, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about LedgerProof LAIN — Verified Evidence for Agents: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.