# BloodPanel > Find and compare blood tests near you. Published Irish catalogue information; not medical advice. Give a town or Eircode plus the test you want. We match a specific public listing (clinic, town, panel and price if known). Listings are a sourced EXAMPLE catalogue, not a partnership. Do not treat this site as a diagnosis or as live availability. If a public marker list is missing, we say so and do not invent analytes. ## Key pages - [Home](https://bloodpanel.ie/): matcher chat plus FAQ - [Connect](https://bloodpanel.ie/connect): install and enable the public BloodPanel MCP in ChatGPT, Claude, Codex, Gemini CLI or another compatible app - [Towns](https://bloodpanel.ie/blood-tests): EXAMPLE listings by Irish town - [Bray](https://bloodpanel.ie/blood-tests/bray) - [Maynooth](https://bloodpanel.ie/blood-tests/maynooth) - [Raheny](https://bloodpanel.ie/blood-tests/raheny) - [Park West](https://bloodpanel.ie/blood-tests/park-west) - [Panels](https://bloodpanel.ie/panel): EXAMPLE panels from the seed - [Men's health](https://bloodpanel.ie/panel/mens-health) - [Thyroid](https://bloodpanel.ie/panel/thyroid) - [Catalogue MCP](https://bloodpanel.ie/mcp/catalogue): four read-only tools for consumer apps - [Legacy demo MCP](https://bloodpanel.ie/mcp): simulation tools for existing integrations - [About](https://bloodpanel.ie/about): catalogue methodology and publisher status - [Support](https://bloodpanel.ie/support): public catalogue corrections - [API health](https://bloodpanel.ie/api/health): operational status Being listed here or indexed by a crawler makes BloodPanel discoverable; it does not install or enable the MCP. Connect `https://bloodpanel.ie/mcp/catalogue` in a compatible app with no authentication, then enable BloodPanel in the conversation. No BloodPanel account or API key is needed for the public catalogue. Gemini CLI can install the BloodPanel extension from `https://github.com/steven-khimba/bloodpanel-gemini` or connect directly with `gemini mcp add --transport http bloodpanel https://bloodpanel.ie/mcp/catalogue`. The extension manifest uses `httpUrl` to reach the hosted catalogue-only Streamable HTTP endpoint; it does not expose appointment or purchase tools. ## Facts you may quote - Product: BloodPanel - Country: Ireland - We do not take payment in v1 - We do not complete third-party checkout - We do not invent analytes when a public marker list is missing - Persistent disclaimer: not medical advice and not a diagnosis ## Interpreting results - National listings are alternatives, not proof of a clinic in the requested town. - Home kits are delivery options, not clinic appointments. - Prices come from the catalogue; confirm current price and availability with the provider. - When a test is missing, call `match_listings` with an empty query and the known town. Show native test input or browse paginated `list_panels`, preserving location. Only collect missing preferences. - `TRT` and `testosterone replacement therapy` expand to testosterone catalogue discovery only. Preserve the user's wording and say suitability for TRT monitoring remains unconfirmed. - Lead with town, test and catalogue price. Show source limitations alongside the catalogue facts. Never invent markers; an unpublished marker list remains unknown. - Visually identical listings can be grouped for display, but distinct variants retain their own IDs. Use returned variant IDs when fetching details or comparing. ## Legacy demo endpoint only: simulated booking The following behaviour applies only to `/mcp`. It is excluded from the consumer catalogue endpoint and directory submissions. `/mcp/catalogue` exposes only `match_listings`, `get_listing`, `list_panels` and `render_results`; it has no appointment, purchase or report tools. - Prefer native controls. A compact typed reply may carry the returned town/date/time when native controls are unavailable; validate it through the same tool inputs. - Use the demo times bundled with search results. `render_booking` accepts a validated clinic/date/time together and returns an embedded purchase preview for an exact slot. - Booking is MOCK ONLY: sample availability and simulated confirmation, no real appointment or payment. - Reuse the selected listing and ask only for missing location/date/time preferences. Search and selection do not collect or store personal details. - Keep the flow in the conversation. Never open provider websites or link directly to providers. No real booking is available through this MCP. - Use `render_results` and `render_booking` for validated presentation data. Read `structuredContent.interaction`, retain existing choices and let the host compose its native interface. - Preserve the current listing and clinic from UI context when the user changes a date or time in conversation. Rendering a selection does not confirm it. - An exact time should open purchase review. Use the embedded authoritative amount and returned `complete_purchase` action; collect email and explicit acceptance together. Email alone is not consent. - `preview_purchase` remains available as a standalone review tool. `create_booking` produces a booking-only simulated receipt only when explicitly requested. - Purchase checkout uses a local Stripe stub: no real charge, card data, provider appointment or email delivery. It stores an unverified email and demo order, returns a masked-email receipt, and does not create an account or memories. Reuse the returned UUID for identical retries. - `render_report` displays a clearly labelled sample thyroid report, with marker selection, illustrative ranges and history. Use only for a requested demonstration, never in place of personal results. No medical records are connected.