# Codex Pets Registry (remote · pets.ydb-qdrant.tech)

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

- Trust score: 75/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `pets.ydb-qdrant.tech`: 75/100 (this document), [markdown](https://verifymcp.io/servers/tech-ydb-qdrant-pets-codex-pets-ydb-qdrant/pets.md), [page](https://verifymcp.io/servers/tech-ydb-qdrant-pets-codex-pets-ydb-qdrant/pets)

## Channel facts

- Endpoint: `https://pets.ydb-qdrant.tech/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### Claude

```bash
claude mcp add --transport http tech-ydb-qdrant-pets-codex-pets-ydb-qdrant https://pets.ydb-qdrant.tech/mcp
```

### Codex

```toml
[mcp_servers.tech-ydb-qdrant-pets-codex-pets-ydb-qdrant]
url = "https://pets.ydb-qdrant.tech/mcp"
```

### opencode

```json
{
  "$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

```bash
openclaw mcp add tech-ydb-qdrant-pets-codex-pets-ydb-qdrant --url https://pets.ydb-qdrant.tech/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tech-ydb-qdrant-pets-codex-pets-ydb-qdrant:
    url: "https://pets.ydb-qdrant.tech/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 75, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] TLS certificate: pass → unverified
- [security regression] Stability: 0.23 → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Transport: pass → fail
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-08-01 (score 75, +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.

### 2026-07-31 (score 74, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 70, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 70)

First indexed and scored.

## MCP tools (7)

### `search_pets` (~212 tokens)

Search Codex 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.

Input parameters:

- `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.

### `get_pet` (~99 tokens)

Get Codex 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.

Input parameters:

- `slug` (string, required): Exact slug of an approved public Codex pet.

### `get_install_instructions` (~78 tokens)

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.

Input parameters:

- `slug` (string, required): Exact slug of an approved public Codex pet.

### `get_badge_code` (~86 tokens)

Get README 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.

Input parameters:

- `slug` (string, required): Exact slug of an approved public Codex pet.

### `get_embed_code` (~81 tokens)

Get website 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.

Input parameters:

- `slug` (string, required): Exact slug of an approved public Codex pet.

### `get_card_code` (~86 tokens)

Get animated README 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.

Input parameters:

- `slug` (string, required): Exact slug of an approved public Codex pet.

### `get_pet_request_info` (~69 tokens)

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; no MCP tool exposes those operations. Use search_pets or get_pet for existing approved pets.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tech-ydb-qdrant-pets-codex-pets-ydb-qdrant/pets#diagnostics

## Score history

- 2026-08-03: 75
- 2026-08-02: 75
- 2026-08-01: 75
- 2026-07-31: 74
- 2026-07-30: 72
- 2026-07-29: 72
- 2026-07-28: 71
- 2026-07-27: 70
- 2026-07-26: 70

## Links

- Remote endpoint: https://pets.ydb-qdrant.tech/mcp
- Website: https://pets.ydb-qdrant.tech/
- Changelog RSS feed: https://verifymcp.io/servers/tech-ydb-qdrant-pets-codex-pets-ydb-qdrant/pets/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/tech-ydb-qdrant-pets-codex-pets-ydb-qdrant/pets/changelog.json
- HTML version of this page: https://verifymcp.io/servers/tech-ydb-qdrant-pets-codex-pets-ydb-qdrant/pets