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

yuletide

https://yuletidemarkets.com

Registry code: 3bb72c9270fc7d99

api record

Yuletide Markets finds Christmas markets, Christmas light displays and choose-and-cut Christmas tree farms in the United States near a city, state or ZIP code, optionally within a date range. Each result gives the organizer's own 2026 dates and hours when they have published them (otherwise it says the dates are not announced yet), the official or visitor-bureau page we checked, the date we checked it and the date the answer stops being served. At most 5 results per answer, nearest first. It does not sell tickets, give directions or list every event.

endpoint
https://yuletidemarkets.com/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 yuletide live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is yuletide free to use?
Yes — the hub reached it with no key and no payment.
What tools does yuletide have?
2 tools: find_christmas_markets, find_christmas_lights_and_tree_farms.
Is yuletide 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
100%

90 days 100%· all time 100%

latency
110ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 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.

  • find_christmas_markets unknown 1h ago

    Use this when someone asks where and when Christmas markets (Christkindlmarkts, holiday and craft markets) are near a US city, state or ZIP code, optionally on certain dates in the 2026 season. Returns up to 5 markets, nearest first, each with the organizer's published dates and hours (or a note that the dates are not announced yet), venue, setting, entry type, the official or visitor-bureau page we checked, the date we checked it, the date the answer stops being served and a link to our page. Dates change: always send people to the organizer's site to confirm. Do not use this to list every market, for markets outside the United States, for tickets or lodging, or for light displays and tree farms (find_christmas_lights_and_tree_farms covers those).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "place"
      ],
      "properties": {
        "place": {
          "type": "string",
          "maxLength": 60,
          "minLength": 2,
          "description": "The place to search around: \"City, ST\" (for example \"Edmond, OK\"), a US state, or a 5-digit ZIP code. 2-60 characters. Wildcards and \"all\" are not accepted."
        },
        "end_date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Optional last day, YYYY-MM-DD. Date ranges are limited to 120 days."
        },
        "start_date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Optional first day you want to go, YYYY-MM-DD (2026 season). Leave out to search from today."
        },
        "radius_miles": {
          "type": "integer",
          "maximum": 250,
          "minimum": 5,
          "description": "Optional search radius in miles, 5 to 250. Default 60. Ignored when the place is a whole state."
        }
      }
    }
    arguments 31 lines
  • find_christmas_lights_and_tree_farms unknown 1h ago

    Use this when someone asks where to see Christmas lights (drive-through or walk-through displays) or where to cut their own Christmas tree (choose-and-cut tree farms) near a US city, state or ZIP code, optionally on certain dates in the 2026 season. Choose "light_displays" or "tree_farms". Returns up to 5 results, nearest first, each with the organizer's published dates and hours (or a note that the dates are not announced yet), how it is viewed or what the farm offers, the official or visitor-bureau page we checked, the date we checked it, the date the answer stops being served and a link to our page. Dates change: always send people to the official site to confirm. Do not use this to list every display or farm, for places outside the United States, for tickets or lodging, or for Christmas markets (find_christmas_markets covers those).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "place",
        "kind"
      ],
      "properties": {
        "kind": {
          "enum": [
            "light_displays",
            "tree_farms"
          ],
          "type": "string",
          "description": "\"light_displays\" for Christmas light displays, \"tree_farms\" for choose-and-cut Christmas tree farms."
        },
        "place": {
          "type": "string",
          "maxLength": 60,
          "minLength": 2,
          "description": "The place to search around: \"City, ST\" (for example \"Edmond, OK\"), a US state, or a 5-digit ZIP code. 2-60 characters. Wildcards and \"all\" are not accepted."
        },
        "viewing": {
          "enum": [
            "drive_through",
            "walk_through"
          ],
          "type": "string",
          "description": "Optional, light displays only: only drive-through or only walk-through displays. Ignored for tree farms."
        },
        "end_date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Optional last day, YYYY-MM-DD. Date ranges are limited to 120 days."
        },
        "start_date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Optional first day you want to go, YYYY-MM-DD (2026 season). Leave out to search from today."
        },
        "radius_miles": {
          "type": "integer",
          "maximum": 250,
          "minimum": 5,
          "description": "Optional search radius in miles, 5 to 250. Default 60. Ignored when the place is a whole state."
        }
      }
    }
    arguments 48 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 3bb72c9270fc7d99.

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

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.