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

mcp-registry/io.ledgerproofhq/lain · v1.0.0

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
degraded
Last checked 2026-11-22 19:07 UTC · handshake 893ms

As of 2026-11-22 19:07 UTC, the LedgerProof LAIN — Verified Evidence for Agents MCP server is degraded with a Glimind reliability score of 46/100 (grade D). Over the last 30 days it answered 59.2% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 3 minutes.

uptime (30d checks)
59.2%
checks observed
2,471
outages (90d)
4
tools
9

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

Point your MCP client at this streamable-http endpoint: https://ledgerproofhq.io/api/lain/mcp

Agent-readiness: D (69/100)

D (69/100): 1 error(s), 2 warning(s) across 9 tool(s); ~2,606 tokens of tool definitions.
Scores higher than 3% of 27,664 MCP servers Glimind has audited.
Its tool list costs an agent ~2,606 tokens per session — more than 55% of servers.
69 → 69 since 2026-11-10
no tool-poisoning patterns
Descriptions59
Safety hints30
Schemas100
Protocol100
Stability100
Token cost100
Reliability20
Client compatibility70

What to fix (4)

Up 42.1% of the time over the last 30 days; median recovery 3 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

9 of 9 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: discover_capabilities, discover_opportunities, fund_opportunity, get_job, get_sample_receipt and 4 more

22 parameter(s) across 4 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: get_job, request_capability, resolve_confidence, subject_evidence_graph

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.ledgerproofhq%2Flain/fixes

get_job 1 change
{
  "name": "get_job",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "job_id"
    ],
    "properties": {
      "job_id": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_sample_receipt 1 change
{
  "name": "get_sample_receipt",
  "description": "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 you",
  "inputSchema": {
    "type": "object",
    "properties": {
      "content_hash": {
        "type": "string",
        "description": "sha256 hex of your output/state"
      },
      "task_summary": {
        "type": "string",
        "description": "or a short text description; it will be hashed for you"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
resolve_confidence 1 change
{
  "name": "resolve_confidence",
  "description": "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). Th",
  "inputSchema": {
    "type": "object",
    "required": [
      "subject"
    ],
    "properties": {
      "need": {
        "type": "string",
        "description": "what you are trying to establish, e.g. 'counterparty has no sanctions or recalls'"
      },
      "dry_run": {
        "type": "boolean",
        "description": "true = free preview: evidence + quote, no charge"
      },
      "sources": {
        "type": "array",
        "items": {
          "enum": [
            "us-sec-edgar",
            "fda-drug-recalls",
            "fda-drugsfda",
            "fda-device-510k",
            "fda-device-pma",
            "un-sanctions",
            "eu-sanctions"
          ],
          "type": "string"
        }
      },
      "subject": {
        "type": "string",
        "description": "entity, product, or firm name (2-120 chars)"
      },
      "x_payment": {
        "type": "string",
        "description": "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 settle inline from your own wallet."
      },
      "settlement": {
        "enum": [
          "x402",
          "m2m"
        ],
        "type": "string",
        "description": "x402 = settle autonomously in USDC on Base from your OWN wallet (no credential) - the DEFAULT for cold callers; m2m = enrolled machine-to-machine"
      },
      "budget_cents": {
        "type": "integer",
        "description": "max you will spend"
      },
      "current_confidence": {
        "type": "number",
        "description": "0..1, your confidence now"
      },
      "required_confidence": {
        "type": "number",
        "description": "0..1, your policy threshold"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.ledgerproofhq/lain"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.ledgerproofhq/lain"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fio.ledgerproofhq%2Flain.svg)](https://glimind.com/server/mcp-registry%2Fio.ledgerproofhq%2Flain?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.ledgerproofhq%2Flain?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.ledgerproofhq%2Flain.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:be159e68a7b72e55…, first seen 2026-10-17, included at leaf 9809 of 384,933. Version history · verify what your client received.

Working alternatives

Tools (9)

Compare: most reliable other servers · most reliable knowledge servers · most reliable finance servers · most reliable payments servers · most reliable security servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the LedgerProof LAIN — Verified Evidence for Agents MCP server down right now?

As of 2026-11-22 19:07 UTC, the LedgerProof LAIN — Verified Evidence for Agents MCP server is degraded with a Glimind reliability score of 46/100 (grade D). Over the last 30 days it answered 59.2% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 3 minutes.

How many tools does LedgerProof LAIN — Verified Evidence for Agents MCP server provide?

LedgerProof LAIN — Verified Evidence for Agents MCP server advertises 9 tools, including discover_capabilities, discover_opportunities, fund_opportunity, get_job, get_sample_receipt.

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

Point your MCP client at this streamable-http endpoint: https://ledgerproofhq.io/api/lain/mcp

Is the LedgerProof LAIN — Verified Evidence for Agents MCP server safe to connect to an AI agent?

Glimind scanned all 9 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of LedgerProof LAIN — Verified Evidence for Agents MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve