Unstable preview. Pages, data and API fields can change or break without notice, so please don't rely on this for anything critical yet. See what has changed.
Agent Service Directory

Zovo Bingo Card Maker

MCP server · bingo-cards.zovo.one · found in a public list · checked since 2026-10-25

Live, handshake completed · latest check

As JSON

https://bingo-cards.zovo.one/mcp MCP endpoint (Streamable HTTP)

The name is the registry's label, not ours. Not reviewed by a person. See 156 endpoints from zovo.one.

Our checks

An unpaid request daily, from eastern North America

Last 1 checks, oldest to newest; room for 29 more

1 passed, 0 failed, 29 not run.

Passed, 30 daysshort history1 of 1 run
Checks missed0in 30 days
Response, latest587 mswhole handshake
Scheduledailyset by usage; rule below
Checked since2026-10-25under 1 day
Freshnessfreshagainst its schedule

Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.

Response times

WindowChecksTimeoutsMedian90th95th99thFastestSlowest
24 hourssince 2026-10-2510——————
7 dayssince 2026-10-2510——————
30 dayssince 2026-10-2510——————

Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.

Details

Tools listed by the server

generate_bingo_cardsgenerate_goal_bingoshow_bingo_caller

Tools
3
This list since
2026-10-25
First listed to us
2026-10-25
List changes, 90 days
0

Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions

Access

Our latest check
Nothing asked
Stated
not stated
Payment model
not known
Currency
not known

"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions

Interface it declares

Protocol
MCP 2025-06-18
Capabilities
resourcestools
Transports
streamable-http

As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions

Calls it declares

  • generate_bingo_cards mode items card_count grid_size free_space free_label title accent_color unique_lines paper cards_per_page seed → view title mode grid free_space
  • show_bingo_caller mode items grid_size free_space card_count seed unique_lines list_code called action card_number pattern title → view title mode action total_items
  • generate_goal_bingo goals* year title subtitle grid_size free_space center_label shuffle seed completed accent_color paper → view title subtitle grid_size cells

From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.

Listing

In the capability tree: Other (not placed in a branch yet) (primary). Placed by keyword rules (placement-rules/3, tree/3) on 2026-10-25. Wrong place? Tell us.

In the index only: does not meet every one of our listing criteria (listing-criteria/6): ✗ what it does is unclear to our placement; ✓ its latest check passed.

Recent probes

WhenResultTime to headers

cloudflare:EWR
Live, handshake completed HTTP 200 587 ms

What these figures do not show

  • A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
  • Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
  • Limited evidence: monitored for under 1 day (less than 30).

Something wrong here?

Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.

Machine-readable: /api/v1/services/cand_3bec1c4e514fa318