Zovo Tally Import
REMOTE · TALLY-IMPORT.ZOVO.ONE
Convert a bank statement to Tally XML that you can import into TallyPrime or Tally ERP 9.
Available components
Last scanned (21 hours ago)
Scores higher than 71% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1552 tokens (~517/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 8 Nov 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://tally-import.zovo.one/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 1a6be51dae225a780e14b5b59cd24fa3 |
| SANs: zovo.one, *.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tally-import.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| one. | DS published | 64939 | 8 | Verified |
| zovo.one. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tally-import.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://tally-import.zovo.one/mcp | HTTPS enforced | 301 | https://tally-import.zovo.one/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
convert_statement_to_tally Convert bank statement to Tally XML ~680
Use this when the user attaches a bank statement (text PDF, CSV or Excel from net banking) and wants it as Tally XML: "bank statement to tally xml", "import bank statement in tally prime", "excel to tally". Builds Payment, Receipt and Contra vouchers against the bank ledger, maps narrations to ledgers with keyword rules (unmatched rows go to a suspense ledger), checks each voucher balances and that opening + rows = closing, and returns the vouchers XML, a ledgers XML and an Excel review sheet. Does not read scans or photos (use generate_tally_vouchers with the rows you can read), does not post into Tally, and is not for GST returns or sales invoices.
| Name | Type | Req | Description |
|---|---|---|---|
| auto_contra | boolean|string|null | – | Book ATM withdrawals and cash deposits as Contra vouchers against the cash ledger. Default true. |
| bank_ledger | string|number|null | – | Your bank ledger name exactly as in Tally, e.g. HDFC Bank A/c. Default: Bank Account. |
| bank_ledger_group | string|number|null | – | Group of the bank ledger in the ledgers file: Bank Accounts (default) or Bank OD A/c. |
| cash_ledger | string|number|null | – | Cash ledger for ATM withdrawals and cash deposits (booked as Contra), e.g. Cash. Default: Cash. |
| closing_balance | number|string|null | – | Closing balance if the file has none, e.g. 98450.00. With the opening balance it proves no row is missing. |
| company | string|number|null | – | Optional Tally company name, e.g. Sharma Traders 2026-27. Leave empty to import into the company open in Tally. |
| date_order | string|number|null | – | Order of numeric dates: DMY (default, 02/04/2026 = 2 April) or MDY. Detected from the file when a day is above 12. |
| file | object | yes | The bank statement to convert: a text PDF, or the CSV or Excel (.xlsx) download from net banking, e.g. hdfc-april-2026.pdf. |
| ledger_rules | – | – | Narration keyword to ledger rules, first match wins, e.g. [{"match":"SALARY","ledger":"Salary Payable"},{"match":"GST","ledger":"GST Payable"}] or text "SALARY=Salary Payable; RENT=Rent". Rows that m… |
| opening_balance | number|string|null | – | Opening balance if the file has none, e.g. 125000.50 or "1,25,000.50 Cr". Used to check the total. |
| statement_year | number|string|null | – | Year for dates printed without one, e.g. 2026, or a financial year like "FY 2026-27" (April to December 2026, January to March 2027). |
| suspense_ledger | string|number|null | – | Ledger for rows that match no rule, e.g. Suspense. Default: Suspense. |
| voucher_type_names | – | – | Only if you renamed voucher types in Tally, e.g. {"payment":"Bank Payment","receipt":"Bank Receipt"}. Defaults: Payment, Receipt, Contra. |
| Name | Type | Req | Description |
|---|---|---|---|
| bank_ledger | string | yes | – |
| downloads | object | yes | – |
| financial_years | array | yes | – |
| import_steps | string | yes | – |
| ledgers | array | yes | – |
| ledgers_count | object | – | – |
| not_imported | array | yes | – |
| not_imported_count | number | yes | – |
| preview | array | yes | – |
| preview_count | object | – | – |
| reconciliation | object | yes | – |
| source | object | yes | – |
| suspense_count | number | yes | – |
| totals | object | yes | – |
| unread_lines | number | yes | – |
| vouchers | object | yes | – |
| warnings | array | yes | – |
| xml_check | string | yes | – |
No examples provided.
generate_tally_vouchers Make Tally vouchers from transactions ~773
Use this when the user wants bank statement to Tally XML from rows they pasted, typed or showed in a statement photo or table: "bank statement to tally entry", "tally xml format for bank statement". First convert what the user gave into transaction objects (date, narration, withdrawal or deposit, balance, optional ledger); pass raw pasted text in `text` only if you cannot. Returns Payment, Receipt and Contra vouchers against the bank ledger, keyword ledger rules with a suspense fallback, a balance check to the paisa, the vouchers XML, a ledgers XML and an Excel review sheet. Do not use when a statement file is attached (use convert_statement_to_tally); does not post into Tally or file GST.
| Name | Type | Req | Description |
|---|---|---|---|
| auto_contra | boolean|string|null | – | Book ATM withdrawals and cash deposits as Contra vouchers against the cash ledger. Default true. |
| bank_ledger | string|number|null | – | Your bank ledger name exactly as in Tally, e.g. HDFC Bank A/c. Default: Bank Account. |
| bank_ledger_group | string|number|null | – | Group of the bank ledger in the ledgers file: Bank Accounts (default) or Bank OD A/c. |
| cash_ledger | string|number|null | – | Cash ledger for ATM withdrawals and cash deposits (booked as Contra), e.g. Cash. Default: Cash. |
| closing_balance | number|string|null | – | Closing balance if the file has none, e.g. 98450.00. With the opening balance it proves no row is missing. |
| company | string|number|null | – | Optional Tally company name, e.g. Sharma Traders 2026-27. Leave empty to import into the company open in Tally. |
| date_order | string|number|null | – | Order of numeric dates: DMY (default, 02/04/2026 = 2 April) or MDY. Detected from the file when a day is above 12. |
| ledger_rules | – | – | Narration keyword to ledger rules, first match wins, e.g. [{"match":"SALARY","ledger":"Salary Payable"},{"match":"GST","ledger":"GST Payable"}] or text "SALARY=Salary Payable; RENT=Rent". Rows that m… |
| opening_balance | number|string|null | – | Opening balance if the file has none, e.g. 125000.50 or "1,25,000.50 Cr". Used to check the total. |
| statement_year | number|string|null | – | Year for dates printed without one, e.g. 2026, or a financial year like "FY 2026-27" (April to December 2026, January to March 2027). |
| suspense_ledger | string|number|null | – | Ledger for rows that match no rule, e.g. Suspense. Default: Suspense. |
| text | – | – | Fallback only: pasted statement text or CSV when you cannot build the objects, e.g. "02/04/2026 NEFT ACME 25,000.00 Cr 1,45,000.00". |
| transactions | – | – | The bank rows as objects in statement order, e.g. [{"date":"02/04/2026","narration":"NEFT-ACME TRADERS","deposit":"25,000.00"},{"date":"03/04/2026","narration":"ATM WDL MG ROAD","withdrawal":5000}].… |
| voucher_type_names | – | – | Only if you renamed voucher types in Tally, e.g. {"payment":"Bank Payment","receipt":"Bank Receipt"}. Defaults: Payment, Receipt, Contra. |
| Name | Type | Req | Description |
|---|---|---|---|
| bank_ledger | string | yes | – |
| downloads | object | yes | – |
| financial_years | array | yes | – |
| import_steps | string | yes | – |
| ledgers | array | yes | – |
| ledgers_count | object | – | – |
| not_imported | array | yes | – |
| not_imported_count | number | yes | – |
| preview | array | yes | – |
| preview_count | object | – | – |
| reconciliation | object | yes | – |
| source | object | yes | – |
| suspense_count | number | yes | – |
| totals | object | yes | – |
| unread_lines | number | yes | – |
| vouchers | object | yes | – |
| warnings | array | yes | – |
| xml_check | string | yes | – |
No examples provided.
How do I install the Zovo Tally Import MCP server?
Zovo Tally Import is a hosted endpoint at https://tally-import.zovo.one/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · tally-import.zovo.one
claude mcp add --transport http theluckystrike-tally-import 'https://tally-import.zovo.one/mcp'
What is the Zovo Tally Import MCP server?
Zovo Tally Import is an MCP server listed in the public MCP registry as io.github.theluckystrike/tally-import. Convert a bank statement to Tally XML that you can import into TallyPrime or Tally ERP 9. This page covers its hosted endpoint (https://tally-import.zovo.one/mcp).
Is the Zovo Tally Import MCP server safe to use?
Zovo Tally Import scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Zovo Tally Import MCP server expose?
Zovo Tally Import exposes 2 tools: convert_statement_to_tally, generate_tally_vouchers. Their descriptions and schemas cost roughly 1,453 tokens of context every time the server is loaded.
Does the Zovo Tally Import MCP server require authentication?
No. We connected to Zovo Tally Import without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zovo Tally Import MCP server still maintained?
Zovo Tally Import is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Zovo Tally Import MCP server?
VerifyMCP ran 14 checks on Zovo Tally Import, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.