Zovo Baby Names
REMOTE · BABY-NAMES.ZOVO.ONE
US baby name trends & finder
Available components
Last scanned (27 minutes ago)
Scores higher than 64% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Education and Research
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability70
- 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 1068 tokens (~356/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 Management3
- Stability observed for 1 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
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.
- 23 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 22 Oct 26 73
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 23 Oct 2026 · Probed https://baby-names.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 | 2e7b9b2e68b9e1370e231e4974cac9a1 |
| SANs: zovo.one, baby-names.zovo.one, *.baby-names.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 baby-names.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://baby-names.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://baby-names.zovo.one/mcp | HTTPS enforced | 301 | https://baby-names.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 →
find_baby_names Find baby names ~702
Use this when the user wants baby name ideas or lists filtered by sex, first letter, ending, letters contained, length, syllables, 2025 popularity (e.g. "familiar but not common" = rank 201-1000), rising names, vintage names (popular 1910-1930, rare now), names popular in an era, or unisex names (40-60% girls). Returns matching names with 2025 rank, births and trend from US Social Security data. Does not give meanings, origins, religious or astrological criteria; do not use for non-US popularity.
| Name | Type | Req | Description |
|---|---|---|---|
| contains | string | – | Name contains these letters anywhere, e.g. "rose". |
| ends_with | string | – | Name ends with these letters, e.g. "lyn". |
| era_from | integer | – | Era start year for 'popular back then', e.g. 1950. |
| era_max_rank | integer | – | Rank a name must have reached in some era year, e.g. 100. Default 300. |
| era_to | integer | – | Era end year, e.g. 1959. |
| limit | integer | – | How many names to return, 1-60, e.g. 30 (default). |
| max_length | integer | – | Maximum letters, e.g. 6. |
| max_syllables | integer | – | Maximum syllables (approximate), e.g. 2. |
| min_births_2025 | integer | – | Minimum US births in 2025, e.g. 100. Default 50 when rising_years is set, else 0. |
| min_length | integer | – | Minimum letters, e.g. 3. |
| min_syllables | integer | – | Minimum syllables (approximate), e.g. 2. |
| popularity | string | – | 2025 rank band: top_100 (1-100), common (101-200), familiar (201-1000, familiar but not common), uncommon (1001-5000), rare (5001 or lower). Example: familiar. |
| rank_max | integer | – | Highest 2025 rank number to include, e.g. 1000. |
| rank_min | integer | – | Lowest 2025 rank number to include, e.g. 200. |
| rising_years | integer | – | Only names with more births in 2025 than N years earlier, sorted by growth, e.g. 10 (compares 2015 to 2025). |
| sex | string | – | girl, boy or any (default any: girls and boys listed separately), e.g. girl. |
| sort | string | – | Order: popular (most 2025 births), rising (biggest growth), alphabetical, rarest (fewest 2025 births). Default popular, or rising with rising_years. |
| starts_with | string | – | Name begins with these letters, case-insensitive, e.g. "a" or "el". |
| unisex | boolean | – | true = names where girls are 40-60% of 2016-2025 US births (at least 100 births in that period). Example: true. |
| vintage | boolean | – | true = vintage names: top 300 in some year 1910-1930 and outside the 2025 top 1,000. Example: true. |
| Name | Type | Req | Description |
|---|---|---|---|
| change_since | number | yes | – |
| filters | array | yes | – |
| kind | string | yes | – |
| names | array | yes | – |
| note | string | yes | – |
| sort | string | yes | – |
| source | string | yes | – |
| total_matches | number | yes | – |
No examples provided.
find_name_trend Find name popularity trend ~274
Use this when the user asks how popular a baby name is or was, its rank or number of babies in a year, its trend, peak year, or wants to compare up to 5 names (e.g. "how popular is Olivia", "Emma vs Ava since 1990", "what rank was Jennifer in 1975"). Returns US Social Security birth counts per year 1880-2025, SSA ranks (top 1,000 for past years; listed names in 2025), peak year, highest rank, 10-year change, girls/boys split and other spellings, with a chart. US data only. Does not give name meanings or origins.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | 1 to 5 first names to look up or compare, e.g. ["Olivia", "Charlotte"]. Add (girl) or (boy) to pick a sex per name, e.g. "Avery (boy)". Accents are ignored for lookup (Zoë finds Zoe). |
| sex | string | – | Sex for all names, e.g. girl. Default any: each name uses the sex with more US births in 2016-2025. |
| year | integer | – | Optional single year to report births and rank for, e.g. 1990. |
| Name | Type | Req | Description |
|---|---|---|---|
| data_years | string | yes | – |
| decades | string | yes | – |
| kind | string | yes | – |
| names | array | yes | – |
| not_found | array | yes | – |
| note | string | yes | – |
| source | string | yes | – |
No examples provided.
How do I install the Zovo Baby Names MCP server?
Zovo Baby Names is a hosted endpoint at https://baby-names.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 · baby-names.zovo.one
claude mcp add --transport http theluckystrike-baby-names 'https://baby-names.zovo.one/mcp'
What is the Zovo Baby Names MCP server?
Zovo Baby Names is an MCP server listed in the public MCP registry as io.github.theluckystrike/baby-names. US baby name trends & finder. This page covers its hosted endpoint (https://baby-names.zovo.one/mcp).
Is the Zovo Baby Names MCP server safe to use?
Zovo Baby Names scores 73 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 Baby Names MCP server expose?
Zovo Baby Names exposes 2 tools: find_name_trend, find_baby_names. Their descriptions and schemas cost roughly 976 tokens of context every time the server is loaded.
Does the Zovo Baby Names MCP server require authentication?
No. We connected to Zovo Baby Names without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zovo Baby Names MCP server still maintained?
Zovo Baby Names is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.