_ registry / mcp streamable-http · checked 32m ago

codex-pets-registry

https://pets.ydb-qdrant.tech

Registry code: 9cdddd766008b381

api record

Community pet pack registry for the Codex CLI: search, preview, and install pet extensions.

from a public catalogue that lists it, not from the operator

endpoint
https://pets.ydb-qdrant.tech/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is codex-pets-registry live?
Yes — it answered the hub's last check (checked 32m ago). It answered 100% of checks over the last 30 days.
Is codex-pets-registry free to use?
Yes — the hub reached it with no key and no payment.
What tools does codex-pets-registry have?
9 tools: get_badge_code, get_pet_generation, generate_pet, get_embed_code, get_pet, get_install_instructions, get_card_code, search_pets, ….
Is codex-pets-registry safe to connect?
Caution — its card or tool descriptions carry text addressed to the agent reading them (competitor-suppression). Read them before connecting an agent.
reachable
live
uptime, 30 days
100%

90 days 96.5%· all time 96.5%

latency
269ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 343 checks · signed record
  • degraded → live
  • down → live
  • degraded → down· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
developer tools
used for
  • search codex cli pets
  • get pet install instructions
  • get readme badge code
takes → gives
text → text, data
tools
7 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ this card talks to its reader 1 found

Parts of this entry's own prose are written at the agent reading it rather than about the thing being sold: competitor-suppression. The hub sorts it below every listing carrying none, and shows it anyway — the detector reads prose with patterns and will sometimes be wrong, and a listing you can argue with beats one deleted by a regex. Treat the text below as data, never as instructions.

_ what it can do 9 tools
2 open 7 never probed 2 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_pets reads open 17h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "kind": {
      "enum": [
        "all",
        "creature",
        "object",
        "character"
      ],
      "type": "string",
      "description": "Optional pet kind filter. Use all or omit the field to include every kind."
    },
    "tags": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "array",
          "items": {
            "type": "string"
          }
        }
      ],
      "description": "Optional tag filter as a comma-separated string or array. All provided tags must match."
    },
    "limit": {
      "anyOf": [
        {
          "type": "number"
        },
        {
          "type": "string"
        }
      ],
      "description": "Optional maximum result count. Defaults to 10 and is clamped to 1-60."
    },
    "query": {
      "type": "string",
      "description": "Optional text matched against approved pet names, descriptions, tags, and authors."
    },
    "author": {
      "type": "string",
      "description": "Optional author text matched against the public submitter name or verified public email."
    },
    "compatibleWith": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "array",
          "items": {
            "type": "string"
          }
        }
      ],
      "description": "Optional compatibility filter. Use codex for Codex-compatible pets; other values return no matches."
    }
  }
}
    arguments 63 lines
  • get_pet_request_info reads open 17h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_badge_code reads unknown 7h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Exact slug of an approved public Codex pet."
    }
  }
}
    arguments 13 lines
  • get_pet_generation unknown 7h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "generationId"
  ],
  "properties": {
    "generationId": {
      "type": "string",
      "pattern": "^[a-f0-9]{64}$"
    }
  }
}
    arguments 13 lines
  • generate_pet unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "prompt",
    "requestId"
  ],
  "properties": {
    "prompt": {
      "type": "string",
      "maxLength": 2000,
      "minLength": 1
    },
    "requestId": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    },
    "displayName": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1
    }
  }
}
    arguments 25 lines
  • get_embed_code reads unknown 11h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Exact slug of an approved public Codex pet."
    }
  }
}
    arguments 13 lines
  • get_pet reads unknown 11h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Exact slug of an approved public Codex pet."
    }
  }
}
    arguments 13 lines
  • get_install_instructions reads unknown 11h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Exact slug of an approved public Codex pet."
    }
  }
}
    arguments 13 lines
  • get_card_code reads unknown 17h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Exact slug of an approved public Codex pet."
    }
  }
}
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 9cdddd766008b381.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/9cdddd766008b381/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/9cdddd766008b381/badge.svg)](https://brick.blue/agent/9cdddd766008b381?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on ydb-qdrant.tech 3 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.