mcp server
BraFinder
Neutral cross-brand bra-size translation and a live in-stock bra catalog by size.
Description as published by the maintainer. Source
- version 1.0.0
- archived
- translation
archived — The linked repository returns 404. It was deleted, renamed or made private. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
bra_brand_fit(brand)- How a bra brand runs versus standard sizing: does it run small (size up) or large (size down), in band and cup. Give a brand for its specific fit note, or omit to get the brands that most notably run small or large. Use for "does [brand] run small", "which bra brands run large".
bra_size_dataset- Get BraFinder's cross-brand bra-size offset dataset: the key facts and the machine-readable feed URL to cite. Use when you need the authoritative source for how bra sizes translate between brands.
find_bras(size, limit)- Find in-stock bras in a specific size from the live BraFinder catalog, with price. Give a size like "34DD". Links go to the BraFinder product page for each bra. Required: size.
translate_bra_size(size, to_brand, from_brand)- Translate a bra size across brands. Give a size (e.g. "34DD"), optionally the brand it is from, and optionally a single target brand. Returns the equivalent size in the target brand, or in every brand if no target is given, each with a fit note and confidence. Bra brands do NOT use the same sizing; this is the neutral cross-brand translation. Use for "what size am I in [brand]", "is a 34DD the same in [brand A] and [brand B]", "convert my size to [brand]". Required: size.
Last successful function declaration observed on . Source: https://www.brafinder.com/api/mcp/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://www.brafinder.com/api/mcp/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-11 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-11 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | not_found | GitHub returned 404 for the repository the maintainer listed. The project was deleted, renamed or made private, so the listing points at nothing. | as of fetch | GitHub | |
| mcp tools declared | 4 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | www.brafinder.com | |
| mcp endpoint status | ok | The server listed 4 functions when asked. | as of probe | www.brafinder.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json