# tech.ydb-qdrant.pets/codex-pets-ydb-qdrant

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.0
- **Author:** tech.ydb-qdrant.pets
- **License:** Unknown
- **Endpoints:** streamable-http https://pets.ydb-qdrant.tech/mcp
- **Source:** https://pets.ydb-qdrant.tech/
- **Endpoint health:** reachable (last checked 2026-10-02T01:40:17.482Z, 6 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 38 days

## Security scan

**Assessment scope:** Hosted endpoint only: Forge can assess who publishes it and whether it answers, not the code behind it. No CVE, dependency or source analysis applies, so nothing here is a clean bill for that code.
- **Status:** probed (endpoint answered; no code examined)
- **Scanned:** 2026-09-04T16:36:06.736Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

7 declared. Observed from a live `tools/list` probe.
- `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 alrea
- `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 sea
- `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_
- `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, inst
- `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 pe
- `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, inst
- `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

## Install

**Verdict: review** — Installable, but 3 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- Hosted endpoint only: Forge can assess who publishes it and whether it answers, not the code behind it. No CVE, dependency or source analysis applies, so nothing here is a clean bill for that code.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"codex-pets-ydb-qdrant\": {\n      \"type\": \"http\",\n      \"url\": \"https://pets.ydb-qdrant.tech/mcp\"\n    }\n  }\n}"
```

## Blast radius

Moderate to extensive — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: mutates data; runs on someone else's infrastructure.
- Floor 26, ceiling 50 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/tech.ydb-qdrant.pets%2Fcodex-pets-ydb-qdrant
- Install plan: https://forgeregistry.com/api/v1/packages/tech.ydb-qdrant.pets%2Fcodex-pets-ydb-qdrant/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/tech.ydb-qdrant.pets%2Fcodex-pets-ydb-qdrant
- HTML page: https://forgeregistry.com/registry/tech.ydb-qdrant.pets%2Fcodex-pets-ydb-qdrant
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.