Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Zovo Client Report

REMOTE · CLIENT-REPORT.ZOVO.ONE

Weekly and monthly KPI reports

+3 this week 78 Trust /100

Last scanned (15 hours ago)

Scores higher than 71% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Data and Analytics

Trust breakdown (7 categories)

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
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 1737 tokens (~579/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
What we tested

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 →

Changelog

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.

Diagnostics

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://client-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 26 Oct 2026 24 Jan 2027 ECDSA 256 ECDSA-SHA256 20a5e9ae0ba92223132067eaf30d62ae
SANs: zovo.one, client-report.zovo.one, *.client-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 client-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://client-report.zovo.one/mcp Verified 200
http (plaintext) http://client-report.zovo.one/mcp HTTPS enforced 301 https://client-report.zovo.one/mcp
MCP tools · 2 exposed · ~1,632 tokens

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 →

Tool Tokens
generate_client_report ~928

Use this when the user wants a weekly or monthly client report, a monthly marketing report, a KPI report or a client report template filled with their numbers: metrics for this period and the previous period, typed ("Sessions 12,400 vs 10,900"), pasted as a table, or an uploaded CSV/Excel export with a date column (Google Analytics, Search Console, Meta Ads, Shopify). Returns the changes (absolute and %), rates recomputed from totals (CTR = clicks / impressions), highlights stated from the computed changes only, and a client-ready PDF (title, client, period, KPI tiles with arrows, change chart, optional notes from the user) plus Excel and CSV. Does not connect to analytics or ad accounts, does not invent numbers or reasons, and is not for forecasts.

NameTypeReqDescription
accent_colorstring–Optional: brand colour for the header bar, hex like #1F3A5F or a name like navy, teal. Default navy.
client_namestring|number–Optional: the client's name for the report title, e.g. "Northwind Dental". Default: Client.
currencystring–Optional: currency for money metrics without a symbol, e.g. USD, EUR, GBP. Default USD.
current_period––Optional: dates of this period, e.g. "2026-10-01 to 2026-10-31" or "Oct 2026". Used to split a dated export and as the label in the report.
datastring–Optional: a pasted CSV/TSV table instead of metrics. Either a daily or weekly export with a Date column and metric columns (e.g. "Date,Sessions,Clicks,Impressions\n2026-10-01,410,22,1900"), or a Metr…
date_orderstring–Optional: MDY (US, default) or DMY for dates such as 03/10/2026.
fileobject–Optional: an uploaded CSV or Excel (.xlsx) export, e.g. ga4-sessions.csv, search-console-dates.csv, meta-ads.xlsx or shopify-sales.csv. A Date column plus metric columns, or a Metric | This period |…
lower_is_better––Optional: metric names where a decrease is good, beyond the built-in ones (cost per click, CPA, CPM, bounce rate, position, churn), e.g. ["Refund requests"].
metrics––The metrics, this period and the previous period. Any of: a list like [{"name":"Sessions","current":12400,"previous":10900},{"name":"Revenue","current":"$8,450","previous":"$7,900"}]; an object like…
notesstring–Optional: your own commentary for the client, printed word for word under Notes, e.g. "We launched the new landing page on Oct 14." Never invented by the tool.
pair_orderstring–Optional: current_first (default: "Sessions 1200 1000" means 1,200 now, 1,000 before) or previous_first. Words such as vs, from ... to, or column headers like This month / Last month always win.
paperstring–Optional: letter (default) or A4.
periodstring–Optional for exports with dates: week, month, quarter or auto (default). auto compares calendar months when the data covers whole months, otherwise the latest half of the dates against the half befor…
prepared_bystring–Optional: your name or agency name shown in the header, e.g. "Brightside Marketing".
previous_period––Optional: dates or label of the previous period, e.g. "Sep 2026". Default: the same length right before current_period.
report_titlestring–Optional: report title, e.g. "Monthly SEO report". Default: Weekly report, Monthly report or Performance report from the period.
NameTypeReqDescription
assumptionsarrayyes–
clientstringyes–
countsobjectyes–
downloadsobjectyes–
headlinestringyes–
highlightsarrayyes–
metricsarrayyes–
periodobjectyes–
titlestringyes–
warningsarrayyes–

No examples provided.

summarize_metric_changes ~704

Use this when the user wants a quick period-over-period (week over week, month over month) change table for their metrics without a PDF: "what changed vs last month", "month over month change", "calculate % change for these KPIs". Takes the same inputs as generate_client_report (typed pairs, a pasted table or a CSV/Excel export with dates) and returns absolute and % changes, rates recomputed from totals, computed highlights, and Excel and CSV files. Use generate_client_report when the user wants a client-ready PDF report. Does not connect to analytics accounts and does not explain why numbers changed.

NameTypeReqDescription
currencystring–Optional: currency for money metrics without a symbol, e.g. USD, EUR, GBP. Default USD.
current_period––Optional: dates of this period, e.g. "2026-10-01 to 2026-10-31" or "Oct 2026". Used to split a dated export and as the label in the report.
datastring–Optional: a pasted CSV/TSV table instead of metrics. Either a daily or weekly export with a Date column and metric columns (e.g. "Date,Sessions,Clicks,Impressions\n2026-10-01,410,22,1900"), or a Metr…
date_orderstring–Optional: MDY (US, default) or DMY for dates such as 03/10/2026.
fileobject–Optional: an uploaded CSV or Excel (.xlsx) export, e.g. ga4-sessions.csv, search-console-dates.csv, meta-ads.xlsx or shopify-sales.csv. A Date column plus metric columns, or a Metric | This period |…
lower_is_better––Optional: metric names where a decrease is good, beyond the built-in ones (cost per click, CPA, CPM, bounce rate, position, churn), e.g. ["Refund requests"].
metrics––The metrics, this period and the previous period. Any of: a list like [{"name":"Sessions","current":12400,"previous":10900},{"name":"Revenue","current":"$8,450","previous":"$7,900"}]; an object like…
pair_orderstring–Optional: current_first (default: "Sessions 1200 1000" means 1,200 now, 1,000 before) or previous_first. Words such as vs, from ... to, or column headers like This month / Last month always win.
periodstring–Optional for exports with dates: week, month, quarter or auto (default). auto compares calendar months when the data covers whole months, otherwise the latest half of the dates against the half befor…
previous_period––Optional: dates or label of the previous period, e.g. "Sep 2026". Default: the same length right before current_period.
NameTypeReqDescription
assumptionsarrayyes–
clientstringyes–
countsobjectyes–
downloadsobjectyes–
headlinestringyes–
highlightsarrayyes–
metricsarrayyes–
periodobjectyes–
titlestringyes–
warningsarrayyes–

No examples provided.

Install

How do I install the Zovo Client Report MCP server?

Zovo Client Report is a hosted endpoint at https://client-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 · client-report.zovo.one

# add to Claude Code
claude mcp add --transport http theluckystrike-client-report 'https://client-report.zovo.one/mcp'
Common questions

What is the Zovo Client Report MCP server?

Zovo Client Report is an MCP server listed in the public MCP registry as io.github.theluckystrike/client-report. Weekly and monthly KPI reports. This page covers its hosted endpoint (https://client-report.zovo.one/mcp).

Is the Zovo Client Report MCP server safe to use?

Zovo Client 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 Client Report MCP server expose?

Zovo Client Report exposes 2 tools: generate_client_report, summarize_metric_changes. Their descriptions and schemas cost roughly 1,632 tokens of context every time the server is loaded.

Does the Zovo Client Report MCP server require authentication?

No. We connected to Zovo Client Report without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Zovo Client Report MCP server still maintained?

Zovo Client 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 Client Report MCP server?

VerifyMCP ran 14 checks on Zovo Client 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.