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 Love Story Poster

REMOTE · ANNIVERSARY-POSTER.ZOVO.ONE

Your days together, in print

+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 Productivity and Notes

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 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 829 tokens (~414/item across 2 items; 1 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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.

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

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://anniversary-poster.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 anniversary-poster.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://anniversary-poster.zovo.one/mcp Verified 200
http (plaintext) http://anniversary-poster.zovo.one/mcp HTTPS enforced 301 https://anniversary-poster.zovo.one/mcp
MCP tools · 1 exposed · ~719 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_anniversary_poster ~719

Use this when the user wants to know how many days they have been together, an "our story in numbers" or relationship stats poster, an anniversary gift printable, a days-together counter, or the date of a milestone such as "when is our 1,000th day", "our 100th day" or "500 weeks together". Pass start_date (first date, the day they met, wedding day) and, when given, start_time, time_zone, names and occasion (together, married, engaged, friends, family). Returns the days, weeks, months, years, hours, full moons, weekends, leap days and anniversaries, the next round milestones with dates, a printable poster PDF (Letter, A4, A3, 12x18 in) and an ICS file with those milestones. Does not invent dates: ask for the start date if it is missing. Does not accept future start dates or dates before 1900. Not for countdowns to a future event or for age calculations of a single person.

NameTypeReqDescription
as_ofstring|null–Optional date to count to, e.g. "2026-12-25" for a gift given that day. Default: today.
count_first_dayboolean|string|null–true to count the first day as day 1 (Korean couple style: the 100th day is start + 99 days). Default false: days elapsed, the 1,000-day mark is start + 1,000 days.
date_orderstring|null–Optional order for dates like 03/04/2019: "mdy" (US, default) or "dmy".
milestonesnumber|string|null–How many upcoming milestones to list and put in the calendar file, 1 to 20. Default 8.
namesstring|null–Optional names printed as the poster headline, e.g. "Alex & Sam".
occasionstring|null–together (default), married, engaged, friends or family. Sets the wording, e.g. "1,000 days married".
page_sizestring|null–Poster size: "Letter" (default), "A4", "A3" or "12x18" (inches). Portrait.
reminder_days_beforenumber|string|null–Days before each milestone for the calendar reminder (at 09:00), 0 to 60. Default 7.
start_datestring|null–The day the story began (first date, the day you met, wedding day), e.g. "2019-06-14" or "June 14, 2019". Must not be in the future.
start_timestring|null–Optional time of day it began, e.g. "19:30" or "7:30 pm". Used for the hours count; default midnight.
themestring|null–Colour theme: blush (default), ivory, sage or midnight.
time_zonestring|null–Optional IANA time zone where it began, e.g. "America/Chicago" or "Europe/London". Makes hours count clock changes and dates full moons locally; also sets "today". Default: America/New_York for today…
titlestring|null–Optional small heading, e.g. "Our story in numbers" (default) or "Five years of us".
NameTypeReqDescription
anniversariesnumberyes–
as_ofstringyes–
as_of_sourcestringyes–
assumptionsarrayyes–
day_number_todaynumberyes–
daysnumberyes–
downloadsobjectyes–
full_moonsnumberyes–
hoursnumberyes–
hours_notestring|nullyes–
leap_daysnumberyes–
milestonesarrayyes–
milestones_shownobject––
monthsnumberyes–
namesstring|nullyes–
next_anniversaryobjectyes–
next_full_moonstringyes–
occasionstringyes–
page_sizestringyes–
reminder_days_beforenumberyes–
start_datestringyes–
start_timestring|nullyes–
start_weekdaystringyes–
themestringyes–
time_zonestring|nullyes–
titlestringyes–
warningsarrayyes–
weekendsnumberyes–
weeksnumberyes–
weeks_remainder_daysnumberyes–
years_months_daysobjectyes–
ymd_textstringyes–

No examples provided.

Install

How do I install the Zovo Love Story Poster MCP server?

Zovo Love Story Poster is a hosted endpoint at https://anniversary-poster.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 · anniversary-poster.zovo.one

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

What is the Zovo Love Story Poster MCP server?

Zovo Love Story Poster is an MCP server listed in the public MCP registry as io.github.theluckystrike/anniversary-poster. Your days together, in print. This page covers its hosted endpoint (https://anniversary-poster.zovo.one/mcp).

Is the Zovo Love Story Poster MCP server safe to use?

Zovo Love Story Poster 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 Love Story Poster MCP server expose?

Zovo Love Story Poster exposes 1 tool: generate_anniversary_poster. Their descriptions and schemas cost roughly 719 tokens of context every time the server is loaded.

Does the Zovo Love Story Poster MCP server require authentication?

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

Is the Zovo Love Story Poster MCP server still maintained?

Zovo Love Story Poster 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 Love Story Poster MCP server?

VerifyMCP ran 14 checks on Zovo Love Story Poster, 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.