_ registry / mcp http-sse · checked 3h ago

bordeaux-guru

https://mcp.bordeaux.guru

Registry code: d57d19557926f916

api record

Read-only data server of bordeaux.guru: independent Bordeaux en primeur tasting notes (first-hand, CZ+EN), real appellation climate (Open-Meteo/ERA5), phenology and terroir. Free tier returns samples and teasers; Collector/Cellar members get full data. Always cite 'bordeaux.guru'. Data marked 'údaje château' comes from official château brochures. Investment notes are personal impressions, not investment advice.

endpoint
https://mcp.bordeaux.guru/mcp
protocol
http-sse ·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 bordeaux-guru live?
Yes — it answered the hub's last check (checked 3h ago). It answered 94% of checks over the last 30 days.
Is bordeaux-guru free to use?
Yes — the hub reached it with no key and no payment.
What tools does bordeaux-guru have?
14 tools: get_wine_prices, compare_climate, get_parcel_varieties, get_vintage_profile, get_price_position, about_bordeaux_guru, lookup_lieudit, get_terroir, ….
Is bordeaux-guru safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
94.1%

90 days 96%· all time 96%

latency
302ms

last good check

priced tools
0

of 14 tools

_ answered our checks, 90 days 455 checks · signed record
  • down → live
  • degraded → down· HTTP 500
  • live → degraded· HTTP 500
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
lifestyle & home food & drink
used for
  • get bordeaux wine tasting notes
  • get chateau profiles
  • compare vintage climate by appellation
  • get en primeur wine prices
takes → gives
text → data, text
tools
14 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

_ what it can do 14 tools
1 open 13 never probed 1 of 14 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.

  • get_phenology reads open 24h ago

    Vine phenology windows (budbreak, flowering, veraison, harvest) for a Bordeaux vintage, as reported in official château brochures ('údaje château'). Sparse, documented vintages only.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "vintage": {
      "type": [
        "integer",
        "null"
      ],
      "default": null,
      "description": "Vintage year, e.g. 2025. Omit for the latest documented vintage."
    },
    "appellation": {
      "type": [
        "string",
        "null"
      ],
      "default": null,
      "description": "Optional appellation filter (name or slug)"
    }
  }
}
    arguments 21 lines
  • get_wine_prices reads unknown 19h ago

    En primeur release prices of one Bordeaux wine across vintages, in EUR (ex-négociant, excluding VAT). Public data — available on every tier. Does NOT include the price position against the vintage curve, which is a members' feature on the website.

    mcp-tool

    {
  "type": "object",
  "required": [
    "wine"
  ],
  "properties": {
    "wine": {
      "type": "string",
      "description": "Wine name or slug, e.g. 'chateau-pontet-canet' or 'Pontet-Canet'"
    }
  }
}
    arguments 12 lines
  • compare_climate reads unknown never probed

    Compare growing-season climate aggregates (GDD, heat days, rain, sunshine, ET0…) across Bordeaux appellations and/or vintages. Collector/Cellar members only.

    mcp-tool

    {
  "type": "object",
  "required": [
    "appellations",
    "years"
  ],
  "properties": {
    "years": {
      "type": "string",
      "description": "Comma-separated years, e.g. '2024,2025'"
    },
    "appellations": {
      "type": "string",
      "description": "Comma-separated appellations (names or slugs), e.g. 'pauillac,margaux'"
    }
  }
}
    arguments 17 lines
  • get_parcel_varieties reads unknown 14h ago

    Parcel-level grape varieties of a Bordeaux château (digitized by bordeaux.guru from official château brochures — 'údaje château'). Aggregate for everyone; per-parcel detail (variety × soil × hectares) for members.

    mcp-tool

    {
  "type": "object",
  "required": [
    "chateau"
  ],
  "properties": {
    "chateau": {
      "type": "string",
      "description": "Château name or slug, e.g. 'gazin'"
    }
  }
}
    arguments 12 lines
  • get_vintage_profile reads unknown 21h ago

    Get the bordeaux.guru vintage profile for a year: quality assessment, harvest summary, key events. Older vintages may have no profile but still have bottle tastings — the answer says so.

    mcp-tool

    {
  "type": "object",
  "required": [
    "year"
  ],
  "properties": {
    "year": {
      "type": "integer",
      "description": "Vintage year, e.g. 2024"
    }
  }
}
    arguments 12 lines
  • get_price_position reads unknown 24h ago

    How dear a Bordeaux wine is for its score: its en primeur release price against the price curve of its own vintage. Collector/Cellar members get the number, the expected price and how many comparably scored wines are cheaper. Everyone gets the release price itself.

    mcp-tool

    {
  "type": "object",
  "required": [
    "wine",
    "vintage"
  ],
  "properties": {
    "wine": {
      "type": "string",
      "description": "Wine name or slug, e.g. 'chateau-pontet-canet' or 'Pontet-Canet'"
    },
    "vintage": {
      "type": "integer",
      "description": "Vintage year, e.g. 2024"
    }
  }
}
    arguments 17 lines
  • about_bordeaux_guru reads unknown never probed

    What the bordeaux.guru MCP server offers: data coverage (en primeur tasting notes, appellation climate, phenology, terroir), access tiers and links.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • lookup_lieudit reads unknown 24h ago

    Look up named vineyard sites (lieux-dits) in Bordeaux appellations — cadastral open data mapped by bordeaux.guru (e.g. BAGES or BATAILLEY in Pauillac). Search by name and/or appellation.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "name": {
      "type": [
        "string",
        "null"
      ],
      "default": null,
      "description": "Site name or its part, e.g. 'bages'. Omit to list sites of an appellation."
    },
    "appellation": {
      "type": [
        "string",
        "null"
      ],
      "default": null,
      "description": "Appellation name or slug to limit the search"
    }
  }
}
    arguments 21 lines
  • get_terroir reads unknown 21h ago

    Terroir profile of a Bordeaux appellation from bordeaux.guru: dominant soils, microclimate, relief (real Copernicus DEM), BRGM gravel terraces (Dubreuilh types 1–6) and named vineyard sites (lieux-dits) coverage.

    mcp-tool

    {
  "type": "object",
  "required": [
    "appellation"
  ],
  "properties": {
    "appellation": {
      "type": "string",
      "description": "Appellation name or slug, e.g. 'pauillac', 'saint-emilion'"
    }
  }
}
    arguments 12 lines
  • get_climate_season reads unknown 14h ago

    Real growing-season climate for a Bordeaux appellation and year (source: Open-Meteo/ERA5, stored by bordeaux.guru): temperatures, rain, wind, humidity, sunshine, ET0, radiation. Returns summary aggregates (GDD, heat days, diurnal range…), monthly aggregates, or daily series.

    mcp-tool

    {
  "type": "object",
  "required": [
    "appellation",
    "year"
  ],
  "properties": {
    "year": {
      "type": "integer",
      "description": "Season year, e.g. 2025"
    },
    "appellation": {
      "type": "string",
      "description": "Appellation name or slug, e.g. 'pauillac', 'margaux'"
    },
    "granularity": {
      "type": "string",
      "default": "summary",
      "description": "Granularity: 'summary' (default), 'monthly', or 'daily'"
    }
  }
}
    arguments 22 lines
  • get_chateau reads unknown 14h ago

    Get a château profile from bordeaux.guru: appellation, classification, terroir, vineyard size, typical blend and its tasted wines.

    mcp-tool

    {
  "type": "object",
  "required": [
    "chateau"
  ],
  "properties": {
    "chateau": {
      "type": "string",
      "description": "Château name or slug, e.g. 'chateau-lynch-bages' or 'Lynch-Bages'"
    }
  }
}
    arguments 12 lines
  • get_bottle_tasting reads unknown 19h ago

    Bottle tasting notes from bordeaux.guru: wines tasted from the bottle at events, as opposed to en primeur barrel samples. Returns event, date, vintage, score, drink window and Czech retail price. The written note is for Collector/Cellar members; others get the opening line.

    mcp-tool

    {
  "type": "object",
  "required": [
    "wine"
  ],
  "properties": {
    "wine": {
      "type": "string",
      "description": "Wine name or slug, e.g. 'Marjosse' or 'chateau-marjosse'"
    },
    "vintage": {
      "type": [
        "integer",
        "null"
      ],
      "default": null,
      "description": "Optional vintage in the bottle, e.g. 2018. Omit for all tasted vintages."
    }
  }
}
    arguments 20 lines
  • search_wines reads unknown 19h ago

    Search Bordeaux wines from bordeaux.guru en primeur tastings by name, château or appellation. Returns wine, château, appellation, vintage, score, en primeur release price in EUR, a pointer to any bottle tasting, and URL.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "color": {
      "type": [
        "string",
        "null"
      ],
      "default": null,
      "description": "Optional color filter: red or white"
    },
    "query": {
      "type": "string",
      "description": "Search text — wine name, château name or appellation (e.g. 'pontet', 'margaux')"
    },
    "vintage": {
      "type": [
        "integer",
        "null"
      ],
      "default": null,
      "description": "Optional vintage filter, e.g. 2024"
    },
    "appellation": {
      "type": [
        "string",
        "null"
      ],
      "default": null,
      "description": "Optional appellation name or slug filter"
    }
  }
}
    arguments 36 lines
  • get_tasting_note reads unknown 21h ago

    Get the en primeur tasting note for one wine and vintage from bordeaux.guru: score, summary (CZ+EN), nose/palate/finish, structure, blend, alcohol, yield, aging potential. Free tiers receive a teaser.

    mcp-tool

    {
  "type": "object",
  "required": [
    "wine"
  ],
  "properties": {
    "wine": {
      "type": "string",
      "description": "Wine name or slug, e.g. 'chateau-pontet-canet' or 'Pontet-Canet'"
    },
    "vintage": {
      "type": [
        "integer",
        "null"
      ],
      "default": null,
      "description": "Vintage year, e.g. 2024. Omit for the latest tasted vintage."
    }
  }
}
    arguments 20 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 d57d19557926f916.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d57d19557926f916/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/d57d19557926f916/badge.svg)](https://brick.blue/agent/d57d19557926f916?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.