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 Bingo Card Maker

REMOTE · BINGO-CARDS.ZOVO.ONE

Printable bingo cards & caller

+3 this week 78 Trust /100

Last scanned (22 hours ago)

Scores higher than 76% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Entertainment and Games

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

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

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

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

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

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

  • 23 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 22 Oct 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 4 Nov 2026 · Probed https://bingo-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 2 Oct 2026 31 Dec 2026 ECDSA 256 ECDSA-SHA256 75933b6f97ad69911323b01188fc8472
SANs: zovo.one, bingo-cards.zovo.one, *.bingo-cards.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 bingo-cards.zovo.one. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
one. present 64939 8 Verified
zovo.one. absent 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://bingo-cards.zovo.one/mcp Verified 200
http (plaintext) http://bingo-cards.zovo.one/mcp HTTPS enforced 301 https://bingo-cards.zovo.one/mcp
MCP tools · 3 exposed · ~2,152 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_bingo_cards ~781

Use this when the user wants printable bingo cards: a bingo card generator or bingo card maker for a holiday party, classroom, baby shower, team meeting, or any game with their own words or phrases, or classic number bingo (1-75) or UK 90-ball tickets. Makes 1-200 different cards (3x3, 4x4 or 5x5, free centre on or off) with each item spread evenly, optionally so that no two cards share a winning line. Returns card 1, balance and uniqueness numbers, and links to a cards PDF (1, 2, 4 or 6 per page, cut lines), a caller sheet PDF and a CSV. Does not add pictures, and does not draw items or check claims (use show_bingo_caller). Not for a single personal goals card (use generate_goal_bingo) or for prize or money games.

NameTypeReqDescription
accent_colorstring–Theme colour as hex or a name, e.g. #2B8A3E, red, green, gold, pink, purple, teal, christmas. Default raspberry #C2255C.
card_countinteger–How many different cards (or tickets) to make, 1-200, e.g. 30. Default 30.
cards_per_pageinteger–Cards per printed page: 1, 2, 4 or 6, e.g. 2. Default 2 (6 for 90-ball tickets). Pages get dashed cut lines.
free_labelstring–Text in the free centre square, e.g. FREE (default), Santa, or Baby.
free_spaceboolean–Free centre square on 3x3 and 5x5 cards, e.g. true. Default true for 5x5 and false for 3x3; 4x4 cards have no centre.
grid_sizeinteger–Card size for mode words: 3, 4 or 5 (default 5), e.g. 5. Classic numbers_75 is always 5x5; numbers_90 tickets are always 3x9.
itemsarray–For mode words: the words or phrases to put on the cards, one per entry, e.g. ["Ugly sweater", "Mistletoe", "Hot cocoa"]. Need at least 24 for 5x5 with a free centre, 25 without, 16 for 4x4, 8 or 9 f…
modestring–words (default): your own words or phrases. numbers_75: classic US bingo, 5x5 with B 1-15, I 16-30, N 31-45, G 46-60, O 61-75. numbers_90: UK-style 3x9 tickets with 15 numbers from 1-90, printed in s…
paperstring–Paper size for the PDFs, e.g. letter (default) or a4.
seedinteger–Card set number from an earlier result, e.g. 4242. The same items, options and seed always rebuild the same cards. Leave out for a new random set.
titlestring–Heading printed on every card, e.g. Holiday Party Bingo. Default Bingo.
unique_linesboolean–true = no two cards share an identical winning line (row, column or diagonal), so two players never complete the very same line. Needs enough items; the tool explains if the request is not possible.…
NameTypeReqDescription
balanceobjectyes–
caller_argsobjectyes–
card_1arrayyes–
card_countnumberyes–
cells_per_cardnumberyes–
downloadsobjectyes–
free_labelstringyes–
free_spacebooleanyes–
gridstringyes–
item_countnumberyes–
modestringyes–
pdf_pagesnumberyes–
seednumberyes–
titlestringyes–
uniquenessobjectyes–
viewstringyes–
warningsarrayyes–

No examples provided.

generate_goal_bingo ~527

Use this when the user wants a goal bingo card (new year goal bingo, 2027 bingo card, resolutions bingo, bucket-list bingo): one personal 5x5 card (or 4x4, 3x3) of their own goals with a free centre, title, year and theme colour, as a PNG, SVG and printable PDF. Goals marked completed print with a check mark and the tool counts bingo lines. Needs one goal per square (24 for 5x5 with a free centre). Does not invent goals for the user and does not make sets of party cards (use generate_bingo_cards).

NameTypeReqDescription
accent_colorstring–Theme colour as hex or a name, e.g. #0B7285, teal, gold, purple. Default raspberry #C2255C.
center_labelstring–Text in the centre square, e.g. FREE (default), Be kind to myself, or 2027.
completedarray–Goals already done, written as in goals, e.g. ["Read 12 books"]. They print with a check mark and count toward bingo lines.
free_spaceboolean–Free centre square on 3x3 and 5x5 cards, e.g. true (default).
goalsarrayyesThe goals, one per square, e.g. ["Run a 10K", "Read 12 books", "Learn to make sourdough"]. Exactly 24 for a 5x5 card with a free centre (25 without), 16 for 4x4, 8 for 3x3 with a free centre (9 witho…
grid_sizeinteger–3, 4 or 5 (default 5), e.g. 5.
paperstring–Paper size for the PDF, e.g. letter (default) or a4.
seedinteger–Shuffle number from an earlier result to repeat the same order, e.g. 77.
shuffleboolean–true to mix the goals into a random order, e.g. false (default keeps your order, filled row by row).
subtitlestring–Small line under the title, e.g. One square at a time.
titlestring–Card heading, e.g. Maya's 2027 Bingo. Overrides the year title.
yearinteger–Year for the title, e.g. 2027 gives "2027 Bingo".
NameTypeReqDescription
accentstringyes–
bingo_linesarrayyes–
cellsarrayyes–
center_indexnumberyes–
donearrayyes–
done_countnumberyes–
downloadsobjectyes–
goal_countnumberyes–
grid_sizenumberyes–
seednumber|nullyes–
subtitlestringyes–
titlestringyes–
viewstringyes–
warningsarrayyes–

No examples provided.

show_bingo_caller ~844

Use this when the user is running a bingo game: call or draw the next word or number at random, show what has been called on a big screen, check whether a claimed bingo on card number N is real (which line, at which call, and who won first), or list all cards that have bingo now. Pass the same items and the caller_args (mode, grid_size, free_space, card_count, seed, unique_lines) from generate_bingo_cards, plus everything called so far in order. Draws use secure randomness. Does not make or print cards and does not keep game state between calls: always send the full called list. Not for prize, betting or money games.

NameTypeReqDescription
actionstring–draw (default): call the next item at random. check: verify a claimed bingo on card_number. winners: list every card that has the pattern now. board: show what has been called. Example: check.
calledarray–Everything already called, in call order, exactly as shown on the cards, e.g. ["Mistletoe", "Hot cocoa"] or ["B-12", "N-40", "O-71"]. Empty for a new game.
card_countinteger–How many different cards (or tickets) to make, 1-200, e.g. 30. Default 30.
card_numberinteger–For action check: the card number printed on the claimed card, e.g. 17.
free_spaceboolean–Free centre square on 3x3 and 5x5 cards, e.g. true. Default true for 5x5 and false for 3x3; 4x4 cards have no centre.
grid_sizeinteger–Card size for mode words: 3, 4 or 5 (default 5), e.g. 5. Classic numbers_75 is always 5x5; numbers_90 tickets are always 3x9.
itemsarray–For mode words: the words or phrases to put on the cards, one per entry, e.g. ["Ugly sweater", "Mistletoe", "Hot cocoa"]. Need at least 24 for 5x5 with a free centre, 25 without, 16 for 4x4, 8 or 9 f…
list_codestring–For word games: list_code from caller_args of generate_bingo_cards, e.g. 0k3x9qa. Confirms the items were sent in the same order as when the cards were made, so card numbers match.
modestring–words (default): your own words or phrases. numbers_75: classic US bingo, 5x5 with B 1-15, I 16-30, N 31-45, G 46-60, O 61-75. numbers_90: UK-style 3x9 tickets with 15 numbers from 1-90, printed in s…
patternstring–Winning pattern to check, e.g. line. line: any row, column or diagonal (90-ball: any row). two_lines: two complete lines. four_corners: the 4 corner squares (not for 90-ball). full_card: every square…
seedinteger–Card set number from an earlier result, e.g. 4242. The same items, options and seed always rebuild the same cards. Leave out for a new random set.
titlestring–Game title shown on the caller screen, e.g. Holiday Party Bingo.
unique_linesboolean–true = no two cards share an identical winning line (row, column or diagonal), so two players never complete the very same line. Needs enough items; the tool explains if the request is not possible.…
NameTypeReqDescription
actionstringyes–
calledarrayyes–
called_countnumberyes–
caller_argsobjectyes–
check–yes–
currentstring|nullyes–
modestringyes–
patternstringyes–
remainingnumberyes–
titlestringyes–
total_itemsnumberyes–
viewstringyes–
winners–yes–

No examples provided.

Install

How do I install the Zovo Bingo Card Maker MCP server?

Zovo Bingo Card Maker is a hosted endpoint at https://bingo-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 · bingo-cards.zovo.one

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

What is the Zovo Bingo Card Maker MCP server?

Zovo Bingo Card Maker is an MCP server listed in the public MCP registry as io.github.theluckystrike/bingo-cards. Printable bingo cards & caller. This page covers its hosted endpoint (https://bingo-cards.zovo.one/mcp).

Is the Zovo Bingo Card Maker MCP server safe to use?

Zovo Bingo 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 Bingo Card Maker MCP server expose?

Zovo Bingo Card Maker exposes 3 tools: generate_bingo_cards, show_bingo_caller, generate_goal_bingo. Their descriptions and schemas cost roughly 2,152 tokens of context every time the server is loaded.

Does the Zovo Bingo Card Maker MCP server require authentication?

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

Is the Zovo Bingo Card Maker MCP server still maintained?

Zovo Bingo Card Maker is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.