Codex Pets Registry
REMOTE · PETS.YDB-QDRANT.TECH · SCANNED AUG 21
Search, preview, install community Codex pet packs, and discover the pet request flow.
Available components
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety–
Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Codex Pets Registry MCP server?
Codex Pets Registry is a hosted endpoint at https://pets.ydb-qdrant.tech/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 · pets.ydb-qdrant.tech
claude mcp add --transport http tech-ydb-qdrant-pets-codex-pets-ydb-qdrant 'https://pets.ydb-qdrant.tech/mcp'
{
"mcpServers": {
"tech-ydb-qdrant-pets-codex-pets-ydb-qdrant": {
"url": "https://pets.ydb-qdrant.tech/mcp"
}
}
} {
"servers": {
"tech-ydb-qdrant-pets-codex-pets-ydb-qdrant": {
"type": "http",
"url": "https://pets.ydb-qdrant.tech/mcp"
}
}
} [mcp_servers.tech-ydb-qdrant-pets-codex-pets-ydb-qdrant] url = "https://pets.ydb-qdrant.tech/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tech-ydb-qdrant-pets-codex-pets-ydb-qdrant": {
"type": "remote",
"url": "https://pets.ydb-qdrant.tech/mcp",
"enabled": true
}
}
} openclaw mcp add tech-ydb-qdrant-pets-codex-pets-ydb-qdrant --url 'https://pets.ydb-qdrant.tech/mcp' --transport streamable-http
mcp_servers:
tech-ydb-qdrant-pets-codex-pets-ydb-qdrant:
url: "https://pets.ydb-qdrant.tech/mcp" {
"McpServers": {
"tech-ydb-qdrant-pets-codex-pets-ydb-qdrant": {
"Transport": "http",
"Url": "https://pets.ydb-qdrant.tech/mcp"
}
}
} assistant mcp add tech-ydb-qdrant-pets-codex-pets-ydb-qdrant -t streamable-http -u 'https://pets.ydb-qdrant.tech/mcp'
{
"mcpServers": {
"tech-ydb-qdrant-pets-codex-pets-ydb-qdrant": {
"type": "http",
"url": "https://pets.ydb-qdrant.tech/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 21 Aug 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Aug 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Aug 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Aug 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 3 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.23 → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
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 Aug 2026 · Probed https://pets.ydb-qdrant.tech/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pets.ydb-qdrant.tech. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | present | 2185 | 13 | Verified |
| ydb-qdrant.tech. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pets.ydb-qdrant.tech/mcp | Unreachable | ||
| http (plaintext) | http://pets.ydb-qdrant.tech/mcp | HTTPS enforced |
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 →
get_badge_code Get README badge code ~86
Use for a known approved pet slug when the user needs README badge Markdown, HTML, or SVG URL. Do not use for animated README cards, website iframe embeds, install instructions, or pet discovery; use get_card_code, get_embed_code, get_install_instructions, or search_pets instead.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Exact slug of an approved public Codex pet. |
No output schema declared.
No examples provided.
get_card_code Get animated README card code ~86
Use for a known approved pet slug when the user needs animated README card Markdown, HTML, or GIF URL. Do not use for simple badges, website iframe embeds, install instructions, or pet discovery; use get_badge_code, get_embed_code, get_install_instructions, or search_pets instead.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Exact slug of an approved public Codex pet. |
No output schema declared.
No examples provided.
get_embed_code Get website embed code ~81
Use for a known approved pet slug when the user needs website iframe embed HTML or an embed URL. Do not use for README badges/cards, install instructions, or pet discovery; use get_badge_code, get_card_code, get_install_instructions, or search_pets instead.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Exact slug of an approved public Codex pet. |
No output schema declared.
No examples provided.
get_install_instructions Get install instructions ~78
Use for a known approved pet slug when the user wants CLI or manual install instructions. Do not use to search for pets or inspect general metadata; use search_pets or get_pet instead. This tool is read-only and does not increment install or download counters.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Exact slug of an approved public Codex pet. |
No output schema declared.
No examples provided.
get_pet Get Codex pet ~99
Use when you already have an exact approved pet slug and need the sanitized public pet card, asset URLs, page URL, and install command for that one pet. Use search_pets first when you only have a name/query or need multiple results. Do not use for focused install, badge, embed, card, or request workflow details; use the matching get_* tool instead.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Exact slug of an approved public Codex pet. |
No output schema declared.
No examples provided.
get_pet_request_info Get pet request info ~69
Use when the user wants to request a new Codex pet or understand the public request form fields and reference image limits. Do not use to create, submit, update, or inspect private generation requests; no MCP tool exposes those operations. Use search_pets or get_pet for existing approved pets.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_pets Search Codex pets ~212
Use to discover one or more approved public Codex pet packs by query, kind, tags, author, or Codex compatibility. Prefer this over get_pet when you do not already have an exact slug or need multiple candidates. Do not use for private generation requests or known-slug install/share snippets; use get_pet_request_info or a slug-specific get_* tool instead.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | Optional author name text matched against the public submitter name. |
| compatibleWith | – | – | Optional compatibility filter. Use codex for Codex-compatible pets; other values return no matches. |
| kind | string | – | Optional pet kind filter. Use all or omit the field to include every kind. |
| limit | – | – | Optional maximum result count. Defaults to 10 and is clamped to 1-60. |
| query | string | – | Optional text matched against approved pet names, descriptions, tags, and authors. |
| tags | – | – | Optional tag filter as a comma-separated string or array. All provided tags must match. |
No output schema declared.
No examples provided.
What is the Codex Pets Registry MCP server?
Codex Pets Registry is an MCP server listed in the public MCP registry as tech.ydb-qdrant.pets/codex-pets-ydb-qdrant. Search, preview, install community Codex pet packs, and discover the pet request flow. This page covers its hosted endpoint (https://pets.ydb-qdrant.tech/mcp).
Is the Codex Pets Registry MCP server safe to use?
Codex Pets Registry scores 0 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 Codex Pets Registry MCP server expose?
Codex Pets Registry exposes 7 tools: search_pets, get_pet, get_install_instructions, get_badge_code, get_embed_code, and 2 more. Their descriptions and schemas cost roughly 711 tokens of context every time the server is loaded.
Does the Codex Pets Registry MCP server require authentication?
Its publisher declares no required credentials for Codex Pets Registry. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Codex Pets Registry MCP server still maintained?
Codex Pets Registry has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 2 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.