Zovo Expense Report
REMOTE · EXPENSE-REPORT.ZOVO.ONE
Make an expense report from your receipts and get reimbursed.
Available components
Last scanned (20 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 Usability67
- 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 2034 tokens (~678/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.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 0
- 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://expense-report.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 | 25 Oct 2026 | 23 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 215481b72e1511c13c40ed8879f86f7 |
| SANs: zovo.one, expense-report.zovo.one, *.expense-report.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 expense-report.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://expense-report.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://expense-report.zovo.one/mcp | HTTPS enforced | 301 | https://expense-report.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 →
generate_expense_report Generate expense report ~1,060
Use this when the user wants an expense report or reimbursement form from their receipts: read the receipts, e-mails or chosen charges yourself and send lines as objects, one per business expense, {date, merchant, amount, currency, category}, plus payment method, receipt yes/no, notes, or miles for mileage; for a stay of several nights send {merchant, amount (the stay total), quantity} or {merchant, quantity, unit_price}. Free text is only a fallback: clear lines are read from it, and any line that is ambiguous (several amounts, a breakdown that does not match its total, an unclear multiplier) is not counted and is returned under "Not counted, check these" for you to send again as structured lines. Phrases: "make an expense report from my receipts", "expense reimbursement form", "mileage reimbursement". Send each receipt once at its total; do not add subtotal, tax-included, cash tendered, change or card payment lines. A bank or card statement is not an expense report: ask the user which charges are business expenses and send only those. When free text has a Total that does not match its lines, the Total is used and the line is flagged for a check. Returns a PDF report (employee, department, period, purpose, line table, category subtotals, advances, total due, signature block), an Excel file, and policy flags (missing receipts, duplicates, weekends and holidays, outside the period, alcohol in meals, per-line cap) as warnings. Lines in another currency without a rate stay out of the total. Does not read images itself, look up exchange rates, or submit anything to an employer system.
| Name | Type | Req | Description |
|---|---|---|---|
| advance | number|string|null | – | Optional: cash advance already received, subtracted from the total due, e.g. 200 or "$200". |
| approver | – | – | Optional: manager who approves the report, e.g. Sam Patel. |
| currency | – | – | Optional: currency of the report total, e.g. USD (default), EUR, GBP. |
| date_order | – | – | Optional: MDY (US) or DMY for dates like 03/10/2026. Default: decided once for the whole list (a day above 12 decides it; otherwise day first for GBP, EUR, AUD, NZD and INR reports, month first for o… |
| department | – | – | Optional: department or cost center, e.g. Sales West. |
| employee_name | – | – | Optional: name printed on the report, e.g. Jordan Lee. Left blank for handwriting when not given. |
| exchange_rates | – | – | Optional: rates into the report currency, e.g. {"EUR": 1.08, "GBP": 1.27} (1 EUR = 1.08 USD). A line's own rate or converted amount wins. |
| flag_weekends | boolean|string|null | – | Optional: flag Saturday and Sunday expenses (default true). |
| holiday_country | – | – | Optional: country whose public holidays are flagged, e.g. US (default), GB, CA, or none. |
| line_cap | number|string|null | – | Optional: flag any single line above this amount, e.g. 500. Default: no cap. |
| lines | – | yes | Expense lines, best as objects converted from what the user pasted or photographed: a list like [{"date":"2026-10-02","merchant":"Delta Air Lines","category":"Airfare","amount":412.30,"receipt":true}… |
| mileage_rate | number|string|null | – | Optional: mileage rate in the report currency or in cents, e.g. 0.70, "70 cents" or "0.30 per km". A rate with no unit is per km for km distances and per mile for mile distances. Default for USD repo… |
| period | – | – | Optional: report period, e.g. "October 2026" or "2026-10-01 to 2026-10-15". Lines outside it are flagged. Default: first to last line date (no period flags). |
| purpose | – | – | Optional: business purpose of the trip or period, e.g. Client visit to Acme in Denver. |
| receipt_required_over | number|string|null | – | Optional: receipts are required for items of this amount or more, e.g. 75 (default 75). |
| report_date | – | – | Optional: date printed on the report, e.g. 2026-10-25. Default: today in the timezone you pass, else today in UTC. |
| timezone | – | – | Optional: the user's IANA timezone for the default report date, e.g. Asia/Ho_Chi_Minh or America/New_York. |
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | yes | – |
| downloads | object | yes | – |
| excluded | array | yes | – |
| flags | array | yes | – |
| lines_preview | array | yes | – |
| notes | array | yes | – |
| policy | array | yes | – |
| report | object | yes | – |
| totals | object | yes | – |
No examples provided.
generate_expense_report_from_file Generate expense report from file ~878
Use this when the user attaches a CSV or Excel (.xlsx) list of chosen business expenses and wants an expense report or reimbursement form from it; if you can read the file yourself, prefer sending its expense lines as objects to generate_expense_report. Reads simple user-made sheets (Date, Merchant, Category, Amount, Currency, Payment method, Receipt, Reimbursable, Miles, Notes) and expense-tool exports such as Expensify, Concur, SAP, Navan, Ramp, Brex, Spendesk, Pleo, Payhawk and Zoho Expense. A bank or card statement export (balance, account or booking-date columns, salary rows) is refused: ask the user which charges are business expenses and send only those. Returns the same PDF report, Excel file and policy flags as generate_expense_report. Pasted text sent to generate_expense_report is read the same strict way: clear lines are counted, and ambiguous ones are returned for you to send again as structured lines. Does not read receipt images or PDFs of receipts (read those yourself and use generate_expense_report), and does not submit anything to an employer system.
| Name | Type | Req | Description |
|---|---|---|---|
| advance | number|string|null | – | Optional: cash advance already received, subtracted from the total due, e.g. 200 or "$200". |
| approver | – | – | Optional: manager who approves the report, e.g. Sam Patel. |
| currency | – | – | Optional: currency of the report total, e.g. USD (default), EUR, GBP. |
| date_order | – | – | Optional: MDY (US) or DMY for dates like 03/10/2026. Default: decided once for the whole list (a day above 12 decides it; otherwise day first for GBP, EUR, AUD, NZD and INR reports, month first for o… |
| department | – | – | Optional: department or cost center, e.g. Sales West. |
| employee_name | – | – | Optional: name printed on the report, e.g. Jordan Lee. Left blank for handwriting when not given. |
| exchange_rates | – | – | Optional: rates into the report currency, e.g. {"EUR": 1.08, "GBP": 1.27} (1 EUR = 1.08 USD). A line's own rate or converted amount wins. |
| file | object | yes | The expense list as a CSV or Excel (.xlsx) file with columns such as Date, Merchant, Category, Amount, e.g. october-expenses.xlsx. |
| flag_weekends | boolean|string|null | – | Optional: flag Saturday and Sunday expenses (default true). |
| holiday_country | – | – | Optional: country whose public holidays are flagged, e.g. US (default), GB, CA, or none. |
| line_cap | number|string|null | – | Optional: flag any single line above this amount, e.g. 500. Default: no cap. |
| mileage_rate | number|string|null | – | Optional: mileage rate in the report currency or in cents, e.g. 0.70, "70 cents" or "0.30 per km". A rate with no unit is per km for km distances and per mile for mile distances. Default for USD repo… |
| period | – | – | Optional: report period, e.g. "October 2026" or "2026-10-01 to 2026-10-15". Lines outside it are flagged. Default: first to last line date (no period flags). |
| purpose | – | – | Optional: business purpose of the trip or period, e.g. Client visit to Acme in Denver. |
| receipt_required_over | number|string|null | – | Optional: receipts are required for items of this amount or more, e.g. 75 (default 75). |
| report_date | – | – | Optional: date printed on the report, e.g. 2026-10-25. Default: today in the timezone you pass, else today in UTC. |
| timezone | – | – | Optional: the user's IANA timezone for the default report date, e.g. Asia/Ho_Chi_Minh or America/New_York. |
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | yes | – |
| downloads | object | yes | – |
| excluded | array | yes | – |
| flags | array | yes | – |
| lines_preview | array | yes | – |
| notes | array | yes | – |
| policy | array | yes | – |
| report | object | yes | – |
| totals | object | yes | – |
No examples provided.
How do I install the Zovo Expense Report MCP server?
Zovo Expense Report is a hosted endpoint at https://expense-report.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 · expense-report.zovo.one
claude mcp add --transport http theluckystrike-expense-report 'https://expense-report.zovo.one/mcp'
What is the Zovo Expense Report MCP server?
Zovo Expense Report is an MCP server listed in the public MCP registry as io.github.theluckystrike/expense-report. Make an expense report from your receipts and get reimbursed. This page covers its hosted endpoint (https://expense-report.zovo.one/mcp).
Is the Zovo Expense Report MCP server safe to use?
Zovo Expense Report 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 Expense Report MCP server expose?
Zovo Expense Report exposes 2 tools: generate_expense_report, generate_expense_report_from_file. Their descriptions and schemas cost roughly 1,938 tokens of context every time the server is loaded.
Does the Zovo Expense Report MCP server require authentication?
No. We connected to Zovo Expense Report without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zovo Expense Report MCP server still maintained?
Zovo Expense Report 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 Expense Report MCP server?
VerifyMCP ran 14 checks on Zovo Expense Report, 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.