mcp-registry/com.tallymesh/lc-checker · v1.0.0
As of 2026-10-18 21:41 UTC, the Tallymesh Lc Checker MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Check a letter-of-credit document set for UCP600/ISBP discrepancies before the bank does.
Claude Code
claude mcp add --transport http tallymesh-lc-checker-mcp-server https://tallymesh.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"tallymesh-lc-checker-mcp-server": {
"type": "http",
"url": "https://tallymesh.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
2 of 2 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 →
1 parameter(s) across 1 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 →
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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.tallymesh%2Flc-checker/fixes
{
"name": "get_lc_audit_result",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"job_id"
],
"properties": {
"job_id": {
"type": [
"integer",
"string"
]
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "start_lc_audit",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"documents"
],
"properties": {
"ruleset": {
"enum": [
"lc-presentation"
],
"type": "string",
"description": "omit for the default 39-rule trade-payment set; 'lc-presentation' = 29-rule UCP600/ISBP L/C presentation check"
},
"documents": {
"type": "array",
"items": {
"type": "object",
"required": [
"filename",
"content_base64"
],
"properties": {
"doctype": {
"type": "string",
"description": "optional: LC,INV,BOL,INS,PL,COO,CD,ST,CON,CLR,SGR,SPPB,WB — auto-detected if omitted"
},
"filename": {
"type": "string",
"description": "e.g. LC.pdf, invoice.pdf, bill-of-lading.pdf"
},
"content_base64": {
"type": "string",
"description": "base64 of the file bytes (pdf/png/jpg/xlsx)"
}
}
},
"description": "1-12 documents"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}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/com.tallymesh/lc-checker"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.tallymesh/lc-checker"}) over MCP.
start_lc_audit ~267 tokensget_lc_audit_result ~84 tokensStatic 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. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.tallymesh%2Flc-checker?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.tallymesh%2Flc-checker?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.tallymesh%2Flc-checker.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.tallymesh%2Flc-checker.svg :target: https://glimind.com/server/mcp-registry%2Fcom.tallymesh%2Flc-checker?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:fe91a3739ed58e25…, first seen 2026-10-17, included at leaf 10962 of 23,479. Version history · verify what your client received.
Compare: most reliable other servers
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.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 21:41 UTC, the Tallymesh Lc Checker MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Tallymesh Lc Checker MCP server advertises 2 tools, including get_lc_audit_result, start_lc_audit.
Point your MCP client at this streamable-http endpoint: https://tallymesh.com/mcp
Glimind scanned all 2 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.
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.