
Qdrant API on YDB MCP server
Which servers in the official MCP registry are Qdrant API on YDB's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-15
- Registry nametech.ydb-qdrant.pets/codex-pets-ydb-qdrantverified in the MCP registry
The registry name sits under ydb-qdrant.tech. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-15
- Tools9
- Server calls itselfcodex-pets-registry
- Server version1.1.0
- Protocol version2025-06-18
On 2026-10-15 the server answered initialize and tools/list without a sign-in. First answer in 524 ms.
- Its tools do none of the product's use cases we checked: Point IDE agents at a Qdrant-compatible base URL; Index GitHub repositories for coding agent search; Store embeddings alongside business rows in YDB.
- Checked on 4 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
- What an agent can do with it0 of 3 use cases
- Answeredmeasuring4 of the 7 daily checks it takes to print a share
- Median first answer542 ms
- Space in an agent's context≈ 1,774 tokensthe definitions of all its tools (9), which an agent carries on every turn
- Tool definitionsA · 96 of 100
- Typed results0 of 9 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 2 of 9
What an agent can do with it
- cannot · Point IDE agents at a Qdrant-compatible base URL
- cannot · Index GitHub repositories for coding agent search
- cannot · Store embeddings alongside business rows in YDB
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
search_petsUse 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…
get_petUse 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…
get_install_instructionsUse 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…
get_badge_codeUse 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_embed_codeUse 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…
get_card_codeUse 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_pet_request_infoUse 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…
generate_petUse only when the user requests a new animated pet from a text brief. Starts one server-paid pet generation task (twelve image stages, each with at most one delayed retry after a confirmed connection closure, plus one text/vision request…
get_pet_generationUse to read your generation task by its private generationId. Completed results include a preview, editable name/description/tags in metadata, and downloadable pet.json, spritesheet and ZIP. Edit metadata on the private preview before…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"codex-pets-ydb-qdrant": {
"type": "http",
"url": "https://pets.ydb-qdrant.tech/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http ydb-qdrant https://pets.ydb-qdrant.tech/mcpclaude.ai, ChatGPT and other clients: add https://pets.ydb-qdrant.tech/mcp as a custom connector in the settings.
- tech.ydb-qdrant/gravity-ai-uianswers, 4 toolsverified in the MCP registry
OpenAPI spec
9 paths, read 2026-10-15. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.