mcpbeat Sign in

Codex Pets Registry MCP Server

by ydb-qdrant-pets Your server? Claim it
answering

Codex Pets Registry is answering right now. Last checked 10 min ago. It exposes 9 tools.

Search, preview, install community Codex pet packs, and discover the pet request flow.

Uptime history 91 days of history · worst day 2%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
9
Tools
read from the server
268 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 16

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 27 August 2026. No other catalogue keeps this.

2 Nov a tool description was rewritten generate_pet
1 Nov a tool description was rewritten generate_pet
22 Oct a tool description was rewritten get_pet_generation
18 Oct a tool description was rewritten get_pet_generation
15 Oct a tool description was rewritten generate_pet
13 Oct a tool description was rewritten generate_pet
12 Oct 2 tool descriptions were rewritten generate_pet, get_pet_generation
11 Oct 3 tool descriptions were rewritten4 times that day generate_pet, get_pet_generation, get_pet_request_info
11 Oct 2 tools appeared generate_pet, get_pet_generation
11 Oct a tool changed version
and 2 more, back to 27 August 2026

Nothing serious here today

Today is the operative word: we check Codex Pets Registry every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add codex-pets-ydb-qdrant --transport http https://pets.ydb-qdrant.tech/mcp
Settings → Connectors → Add custom connector, then paste this address
https://pets.ydb-qdrant.tech/mcp
~/.codex/config.toml
[mcp_servers.codex-pets-ydb-qdrant]
url = "https://pets.ydb-qdrant.tech/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "codex-pets-ydb-qdrant": {
      "url": "https://pets.ydb-qdrant.tech/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "codex-pets-ydb-qdrant": {
      "type": "http",
      "url": "https://pets.ydb-qdrant.tech/mcp"
    }
  }
}

Available tools 9

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

pet
get_pet
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.
get_pet_generation
Use to read your generation task by its private generationId. Completed results include a preview, name/description/tags in metadata, and pet.json and spritesheet. An animationRevision without acceptedAt must be explicitly accepted on its private preview before ZIP download, metadata editing or gallery submission. Other completed results include the ZIP. Website jobs may return awaiting_confirmation: open their private preview for the user to confirm the character. Edit metadata on the private preview before submitting for moderation; this read tool never confirms, edits or starts a paid retry. Failed results include error.code, message, hint and automaticRetry=false: stop polling and explain the failure. Do not use to list other tasks, publish results, or start another paid generation; use generate_pet only for a new user-requested task.
get_pet_request_info
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; these manual workflows are separate from generate_pet and get_pet_generation. Use search_pets or get_pet for existing approved pets.
badge
get_badge_code
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.
card
get_card_code
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.
embed
get_embed_code
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.
generate
generate_pet
Use only when the user requests a new animated pet from a text brief. Starts one server-paid pet generation task (one base and eleven animation rows, plus one text/vision request for an editable name, description and tags). Supply a fresh random UUID requestId; reuse it unchanged when retrying the same request. Limits: 2000 accepted tasks/day globally, 100/IP by default, Moscow time; both are operator-configurable. Admin IP allowances can add attempts until midnight; the global allowance still applies. Returns a task ID; poll get_pet_generation. When automatic repair is enabled for a new task, each animation row has at most four image calls including its first call and transport retries; otherwise legacy tasks allow one delayed transport retry. The base retains its legacy retry policy. Successful animations are kept, and automatic repairs keep the same task/quota/expiry. All costs are still recorded. No monetary threshold applies by default; an operator can explicitly enable a shared recorded-spend threshold. The result is unlisted and expires after 24 hours. Do not use to publish a pet, edit an image, or create a manual administrator request. Experimental generation: animations and gaze directions may contain visual errors or look too similar. Review the preview before submitting your pet to moderation. Accepted tasks count toward the limit even if the result is unsuitable. Image requests may be retried under the saved task policy, which can incur additional provider charges.
install
get_install_instructions
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.
pets
search_pets
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.

Endpoints

URLTransportStateLatencyChecked
https://pets.ydb-qdrant.tech/mcp streamable-http answering 193 ms 10 min ago

Alternatives to Codex Pets Registry

same job, measured the same way
Skill Builder MCP
by dmzagent

Search the skill-builder registry and auto-install skills for Claude Code, Cursor, and Codex.

110 installs/wk local only
Skillmd
by skillmd

Search, fetch, lint, and install Agent Skills (SKILL.md) from the SkillMD registry.

875 installs/wk 5 tools answering
TokRepo — AI Asset Registry
by henu-wang

TokRepo MCP: tokrepo_discover, tokrepo_verify, tokrepo_install_plan for reusable AI assets.

112 installs/wk local only
Ailist MCP
by hifriendbot

MCP server for AiList — search and discover Ai projects from Claude Code

53 installs/wk local only
Shipyard
by goshipyard

Ship, discover and review vibe-coded projects on Shipyard, the invite-only feed for AI-built apps.

9 tools answering
CodeY CMS
by fpointerdev

Discover, evaluate, install, and validate generated websites for the self-hosted CodeY CMS.

41 installs/wk local only
oss-search
by sblattj

Fast local and federated OSS code search and repo discovery for AI agents

81 installs/wk local only
Peer Lookup Tools
by peerlookup

Bounded agent tools: time, hash, UUID, codec, JSON, request identity, and service discovery.

8 tools answering

Codex Pets Registry — questions

Answers built from our own checks of this server.

What can Codex Pets Registry do?
It exposes 9 tools, read directly from the server on our last check. Among them: generate_pet, get_badge_code, get_card_code, get_embed_code, get_install_instructions, get_pet and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Codex Pets Registry working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 268 ms. The bar chart above shows every period we have measured.
How do I connect Codex Pets Registry?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Codex Pets Registry need an API key?
No. Codex Pets Registry completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Codex Pets Registry?
It answers our handshake in 268 ms on average, which is faster than 53% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.