mcpbeat

Lc Checker MCP Server

com.tallymesh/lc-checker
answering

Lc Checker is answering right now. Last checked 11 min ago. It exposes 2 tools.

Check a letter-of-credit document set for UCP600/ISBP discrepancies before the bank does.

Uptime history 43 hours of history
43 hours agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
113 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add lc-checker --transport http https://tallymesh.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "lc-checker": {
      "url": "https://tallymesh.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.lc-checker]
url = "https://tallymesh.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "lc-checker": {
      "url": "https://tallymesh.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "lc-checker": {
      "url": "https://tallymesh.com/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

audit
get_lc_audit_result
Poll a TallyMesh audit job and fetch the verdict + per-rule findings (each pinned to a field and cited to the UCP600/ISBP article) + report paths.
start
start_lc_audit
Start a UCP600/ISBP letter-of-credit / trade-document discrepancy audit over a set of documents. Returns a job_id; then call get_lc_audit_result to poll. Decision support, not a guarantee of bank acceptance.

Endpoints

URLTransportStateLatencyChecked
https://tallymesh.com/mcp streamable-http answering 110 ms 11 min ago

Lc Checker — questions

Answers built from our own checks of this server.

What can Lc Checker do?
It exposes 2 tools, read directly from the server on our last check. Among them: get_lc_audit_result, start_lc_audit. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Lc Checker working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 113 ms. The bar chart above shows every period we have measured.
How do I connect Lc Checker?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Lc Checker need an API key?
No. Lc Checker completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Lc Checker?
It answers our handshake in 113 ms on average, which is faster than 81% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.