Skip to content

TallyMesh MCP server

Which servers in the official MCP registry are TallyMesh's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-25

← Back to TallyMesh

Whose server it is
  • Registry namecom.tallymesh/lc-checkerverified in the MCP registry

The registry name sits under tallymesh.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-25
  • Stateanswerschecked 2026-10-25
  • Tools2
  • Server calls itselftallymesh
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-25 the server answered initialize and tools/list without a sign-in. First answer in 44 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: Check letter of credit document sets for discrepancies before bank presentation; Verify amounts, dates and ports match across invoice and bill of lading.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • For "Check letter of credit document sets for discrepancies before bank presentation", the likely first call is start_lc_audit.
  • For "Verify amounts, dates and ports match across invoice and bill of lading", the likely first call is start_lc_audit.
  • Parameters are untyped or undescribed in 1 of 2 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-25
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer97 ms
  • Space in an agent's context≈ 317 tokensthe definitions of all its tools (2), which an agent carries on every turn
  • Tool definitionsB · 75 of 100
  • Typed results0 of 2 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 1 of 2
  • Not saying whether it only reads or can destroy: 2 of 2

What an agent can do with it

  • can do · Check letter of credit document sets for discrepancies before bank presentation
  • can do · Verify amounts, dates and ports match across invoice and bill of lading
  • not sure · Fix flagged fields and export audit reports for records

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers2 tools · read 2026-10-25
  • 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.

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

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "lc-checker": {
      "type": "http",
      "url": "https://tallymesh.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http tallymesh https://tallymesh.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://tallymesh.com/mcp as a custom connector in the settings.

OpenAPI spec

4 paths, read 2026-10-25. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.