Zovo Place Card Maker
REMOTE · PLACE-CARDS.ZOVO.ONE
Printable tent place cards
Available components
Last scanned (12 hours ago)
Scores higher than 71% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Documents and Files
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 Usability69
- 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 957 tokens (~319/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.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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://place-cards.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 place-cards.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://place-cards.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://place-cards.zovo.one/mcp | HTTPS enforced | 301 | https://place-cards.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_escort_cards Generate escort cards and table plan ~402
Use this when the user wants escort cards (flat cards that tell each guest their table, often with meal choice) or a printable table plan list from a guest list. Convert the guest list into guests (name, table, meal). Returns flat 3.5 x 2 in cards, 10 per Letter or A4 page (or 105 x 74 mm, 8 per A4), with crop marks, plus a table plan PDF grouped by table with meal counts. Up to 300 guests. Does not choose seats for guests.
| Name | Type | Req | Description |
|---|---|---|---|
| event_title | – | – | Optional small line on each card, e.g. "Emma & Liam · 12 June 2027" or "Thanksgiving 2026". |
| guests | – | – | The guest list as objects. Convert a pasted list, a spreadsheet or a photo of a seating chart into these fields. Example: [{"name":"Ana Kowalska","table":1,"meal":"Fish"},{"name":"王芳","table":2}]. Up… |
| paper | – | – | letter (default) or A4. |
| show_meal | – | – | Print the meal choice as a small tag. Default true when meals are given. |
| show_table | – | – | Print the table number on the card. Default true when tables are given. |
| size | – | – | Card size: "3.5x2" (default, US 3.5 x 2 in flat) or "a7" (105 x 74 mm flat, 8 per A4 page). |
| sort | – | – | table (default when tables are given: by table, then name), alpha (by full name), last (by last name) or given (list order). |
| text | – | – | Fallback only: a pasted guest list, one guest per line, e.g. "Ana Kowalska, 1, Fish" or CSV with a Name,Table,Meal header. Prefer guests. |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | array | yes | – |
| counts | object | yes | – |
| downloads | object | yes | – |
| flags | array | yes | – |
| flags_count | object | – | – |
| kind | string | yes | – |
| layout | object | yes | – |
| meals | array | yes | – |
| meals_count | object | – | – |
| preview | array | yes | – |
| preview_count | object | – | – |
| tables | array | yes | – |
| tables_count | object | – | – |
| title | string | yes | – |
No examples provided.
generate_place_cards Generate tent place cards ~487
Use this when the user wants place cards printable from a guest list, a place card template, or table name cards for a wedding, dinner or Thanksgiving. Convert the user's guest list, spreadsheet or a photo of a seating chart into guests (name, table, meal); use text only as a fallback. Makes tent-fold cards, 3.5 x 2 in folded (or 105 x 74 mm A7 on A4), 4 per page or 6 per Letter landscape page, with the name on both faces (back face rotated 180°), dashed fold lines, crop marks, an optional event line, table number and meal tag, sorted by table or name. Long names shrink then wrap to 2 lines. Also returns a table plan PDF. Up to 300 guests. Does not seat guests or design invitations.
| Name | Type | Req | Description |
|---|---|---|---|
| event_title | – | – | Optional small line on each card, e.g. "Emma & Liam · 12 June 2027" or "Thanksgiving 2026". |
| guests | – | – | The guest list as objects. Convert a pasted list, a spreadsheet or a photo of a seating chart into these fields. Example: [{"name":"Ana Kowalska","table":1,"meal":"Fish"},{"name":"王芳","table":2}]. Up… |
| paper | – | – | letter (default) or A4. |
| per_page | – | – | 4 (default, portrait) or 6 per page (landscape, US size on Letter only). |
| show_meal | – | – | Print the meal choice as a small tag. Default true when meals are given. |
| show_table | – | – | Print the table number on the card. Default true when tables are given. |
| size | – | – | Card size: "3.5x2" (default, US 3.5 x 2 in folded) or "a7" (105 x 74 mm folded, 4 per A4 sheet). |
| sort | – | – | table (default when tables are given: by table, then name), alpha (by full name), last (by last name) or given (list order). |
| text | – | – | Fallback only: a pasted guest list, one guest per line, e.g. "Ana Kowalska, 1, Fish" or CSV with a Name,Table,Meal header. Prefer guests. |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | array | yes | – |
| counts | object | yes | – |
| downloads | object | yes | – |
| flags | array | yes | – |
| flags_count | object | – | – |
| kind | string | yes | – |
| layout | object | yes | – |
| meals | array | yes | – |
| meals_count | object | – | – |
| preview | array | yes | – |
| preview_count | object | – | – |
| tables | array | yes | – |
| tables_count | object | – | – |
| title | string | yes | – |
No examples provided.
How do I install the Zovo Place Card Maker MCP server?
Zovo Place Card Maker is a hosted endpoint at https://place-cards.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 · place-cards.zovo.one
claude mcp add --transport http theluckystrike-place-cards 'https://place-cards.zovo.one/mcp'
What is the Zovo Place Card Maker MCP server?
Zovo Place Card Maker is an MCP server listed in the public MCP registry as io.github.theluckystrike/place-cards. Printable tent place cards. This page covers its hosted endpoint (https://place-cards.zovo.one/mcp).
Is the Zovo Place Card Maker MCP server safe to use?
Zovo Place Card Maker 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 Place Card Maker MCP server expose?
Zovo Place Card Maker exposes 2 tools: generate_place_cards, generate_escort_cards. Their descriptions and schemas cost roughly 889 tokens of context every time the server is loaded.
Does the Zovo Place Card Maker MCP server require authentication?
No. We connected to Zovo Place Card Maker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zovo Place Card Maker MCP server still maintained?
Zovo Place Card Maker 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 Place Card Maker MCP server?
VerifyMCP ran 14 checks on Zovo Place Card Maker, 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.