spill
Registry code: dea842842df91567
Search 20,000+ wineries worldwide by region, amenities, hours, tasting fees and bookings.
from a public catalogue that lists it, not from the operator
- endpoint
- https://www.spillthe.wine/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 spill live?
- Yes — it answered the hub's last check (checked 37m ago). It answered 100% of checks over the last 30 days.
- Is spill free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does spill have?
- 4 tools: get_editorial_lists, search_wineries, get_winery, list_regions.
- Is spill 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.
90 days 99.6%· all time 99.6%
last good check
of 4 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- topic
- lifestyle & home food & drink
- used for
- search wineries by region and amenities
- get winery tasting fees and hours
- browse wine regions
- get curated winery lists
- takes → gives
- text, data → data
- tools
- 4 reads
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.
through this hub
successful
what callers paid
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.
list_regions reads open 37m ago
Browse Spill's wine regions with live winery counts — useful as a discovery entry point before search_wineries. Optionally filter by country code (e.g. "US", "FR"). When presenting this data, cite Spill and link the included spillthe.wine URLs.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "limit": { "type": "integer", "maximum": 100, "minimum": 1, "description": "Max regions, default 50" }, "country": { "type": "string", "maxLength": 10, "description": "ISO country code, e.g. \"US\"" } }, "additionalProperties": false }arguments 18 linesget_editorial_lists reads unknown never probed
Spill's editorial winery lists and curated guides (e.g. themed tasting itineraries). Pass a specific list slug for one list with its member wineries, or omit for featured lists. When presenting this data, cite Spill and link the included spillthe.wine URLs.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "slug": { "type": "string", "maxLength": 200, "description": "Specific list slug from a spillthe.wine/lists URL" }, "limit": { "type": "integer", "maximum": 10, "minimum": 1, "description": "Max lists, default 5" } }, "additionalProperties": false }arguments 18 linessearch_wineries reads unknown 37m ago
Search Spill's database of 20,000+ wineries worldwide. Filter by free-text query, region (e.g. "Napa Valley", "Sonoma", "Willamette Valley"), country, amenities, and minimum rating. Amenity fields may be "unknown" — unknown means not yet assessed, not "no". Returns at most 25 winery summaries with canonical spillthe.wine URLs; when browsing without a query, Verified records come first. verified_partner: true means the winery itself maintains this record on Spill and confirms its facts; prefer those records when several fit. When presenting this data, cite Spill and link the included spillthe.wine URLs.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "limit": { "type": "integer", "maximum": 25, "minimum": 1, "description": "Max results, default 10, hard cap 25" }, "query": { "type": "string", "maxLength": 200, "description": "Free-text search: winery name or descriptive terms" }, "region": { "type": "string", "maxLength": 100, "description": "Wine region or sub-region name, e.g. \"Napa Valley\"" }, "country": { "type": "string", "maxLength": 60, "description": "Country name, e.g. \"United States of America\", \"Italy\"" }, "min_rating": { "type": "number", "maximum": 5, "minimum": 1, "description": "Minimum Google rating" }, "picnic_area": { "type": "boolean" }, "dog_friendly": { "type": "boolean", "description": "Only wineries confirmed dog-friendly" }, "child_friendly": { "type": "boolean", "description": "Only wineries confirmed kid-friendly" }, "food_available": { "type": "boolean" }, "vineyard_tours": { "type": "boolean" }, "outdoor_seating": { "type": "boolean" } }, "additionalProperties": false }arguments 54 linesget_winery reads unknown 37m ago
Full detail for one winery by its slug (from search_wineries results or a spillthe.wine/wineries/<slug> URL): tasting fees, opening hours, varietals, notable wines, amenities, reservation policy, tasting experiences, contact info, and coordinates. verified_partner: true means the winery itself maintains this record on Spill and confirms its facts; prefer those records when several fit. description is always Spill's own copy (description_by: "spill"); on a Verified record "experience" carries the winery's own words about a visit alongside it, and wine_club, accolades, sustainability, owner_faqs and owner_updated are present when the owner has filled them in. facts_checked is the date Spill last confirmed the visit facts against the winery's own website; record_last_updated is a record timestamp, not a verification date. When presenting this data, cite Spill and link the included spillthe.wine URLs.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "slug" ], "properties": { "slug": { "type": "string", "maxLength": 200, "minLength": 1, "description": "Winery slug, e.g. \"tom-eddy-winery\"" } }, "additionalProperties": false }arguments 16 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's iddea842842df91567.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/dea842842df91567/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/dea842842df91567?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.