LedgerProof LAIN — Verified Evidence for Agents

verify

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "verify"
  }
}

Input Schema

Name	Required	Description	Default
`seq`	No	or the receipt's sequence number
`content_hash`	No	sha256 hex from a receipt (64 hex chars)

Schema Changelog

Changes observed during successful MCP inspections.

AddedAug 2, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden and excels: it discloses the public append-only log source, return behavior for non-existent/altered hashes (found:false), and explicitly limits scope to existence/integrity, not truth. It also notes the response includes read-only endpoints for independent re-checking.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is front-loaded and punchy: 'FREE, no auth, no account: independently verify ANY LedgerProof/LAIN receipt.' Although the description is lengthy, every sentence contributes essential information about inputs, outputs, data source, or scope, making it dense but not verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given there is no output schema or annotations, the description thoroughly covers purpose, input parameters, output semantics, limitations, and the verification philosophy. It is complete enough for an agent to correctly select and invoke this tool without additional context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by clarifying the two parameters are alternatives ('Pass content_hash ... or seq') and that content_hash is the sha256 hex from a receipt, supplementing the schema's descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool verifies LedgerProof/LAIN receipts, with specific inputs (content_hash or seq) and outputs (existence, record time, entry hash, anchor). It is distinct from siblings by its verification focus, which none of the other tools explicitly address.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly frames when to use it ('verify it yourself, do not trust the seller') and notes it is free and requires no auth. However, it does not explicitly name alternatives or define when-not-to-use, so it falls short of a 5 but provides solid contextual guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All LedgerProof LAIN — Verified Evidence for Agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?