# Zovo Place Card Maker (remote · place-cards.zovo.one)

Printable tent place cards

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `place-cards.zovo.one`: 78/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-place-cards/place-cards.md), [page](https://verifymcp.io/servers/theluckystrike-place-cards/place-cards)

## Channel facts

- Endpoint: `https://place-cards.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

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

### Claude

```bash
claude mcp add --transport http theluckystrike-place-cards 'https://place-cards.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-place-cards": {
      "url": "https://place-cards.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-place-cards": {
      "type": "http",
      "url": "https://place-cards.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-place-cards]
url = "https://place-cards.zovo.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-place-cards": {
      "type": "remote",
      "url": "https://place-cards.zovo.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-place-cards --url 'https://place-cards.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-place-cards:
    url: "https://place-cards.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-place-cards": {
      "Transport": "http",
      "Url": "https://place-cards.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-place-cards -t streamable-http -u 'https://place-cards.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-place-cards": {
      "type": "http",
      "url": "https://place-cards.zovo.one/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-19 (score 78, +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.

### 2026-11-17 (score 77, +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.

### 2026-11-15 (score 76, +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.

### 2026-11-13 (score 75, +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.

### 2026-11-11 (score 74, +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.

### 2026-11-09 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 72)

First indexed and scored.

## MCP tools (2)

### `generate_place_cards` (~487 tokens)

Generate tent place cards

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.

Input parameters:

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

Output parameters:

- `assumptions` (array)
- `counts` (object)
- `downloads` (object)
- `flags` (array)
- `flags_count` (object)
- `kind` (string)
- `layout` (object)
- `meals` (array)
- `meals_count` (object)
- `preview` (array)
- `preview_count` (object)
- `tables` (array)
- `tables_count` (object)
- `title` (string)

### `generate_escort_cards` (~402 tokens)

Generate escort cards and table plan

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.

Input parameters:

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

Output parameters:

- `assumptions` (array)
- `counts` (object)
- `downloads` (object)
- `flags` (array)
- `flags_count` (object)
- `kind` (string)
- `layout` (object)
- `meals` (array)
- `meals_count` (object)
- `preview` (array)
- `preview_count` (object)
- `tables` (array)
- `tables_count` (object)
- `title` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-place-cards/place-cards#diagnostics

## Score history

- 2026-11-21: 78
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 76
- 2026-11-15: 76
- 2026-11-14: 75
- 2026-11-13: 75
- 2026-11-12: 74
- 2026-11-11: 74
- 2026-11-10: 73
- 2026-11-09: 73
- 2026-11-08: 72

## Common questions

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

## Links

- Remote endpoint: https://place-cards.zovo.one/mcp
- Website: https://place-cards.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-place-cards/place-cards.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-place-cards/place-cards/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-place-cards/place-cards.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-place-cards/place-cards
