McDonald's Event Radar

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites: Account and token required before any real use: a McDonald's China MCP token. The listing is free, and activating the token is described upstream as free. Get the token yourself, in person, because it needs mobile phone number verification: go to https://open.mcd.cn/mcp , sign in with your mobile phone number, open the console at the top right, click Activate, agree to the service agreement, and copy the token. Then configure the McDonald's China MCP server: name mcd-mcp, type streamablehttp, URL https://mcp.mcd.cn , header Authorization: Bearer <your token>, or set the MCD_MCP_TOKEN environment variable where the skill reads it that way. Keep the token only in your own private client configuration or environment: never commit it, never share it, and never paste it into a shared chat. Upstream states a limit of 600 requests per minute per token (429 above that). This skill also needs Node.js 20 or later to run its bundled scripts (they have no npm dependencies). One upstream difference matters here: its own first use guide sends you to https://open.mcd.cn/mcp/doc for the token (sign in, then Console, then Activate there) and then asks you to paste the token into the chat so the agent can run scripts/setup-connector.mjs for you. That script can also be run by you directly: it takes the token from the MCD_MCP_TOKEN environment variable, from a --token argument, or from a hidden interactive prompt that does not echo, then writes it into your private ~/.workbuddy/mcp.json config file (backing the previous file up first and preserving other servers) and never prints it. Prefer running it yourself, or using the environment variable, over pasting the token into any chat. Install "McDonald's Event Radar" for me. It searches McDonald's China theme events through the official MCP, verifies real bookable sessions store by store, can detect your city at city level with your permission, and draws the results as a local cartoon HTML map. It books only when you explicitly ask, after a full confirmation. Repository: https://github.com/Zafer-Liu/mcd-event-radar (the skill is the whole skill/mcd-event-radar/ folder at the pinned commit: 8 files, listed in the fingerprints below) Pinned version: install the code at commit e06f7df51d620356dd7386745394eaac92a6de25 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/Zafer-Liu/mcd-event-radar into a temporary folder, check out commit e06f7df51d620356dd7386745394eaac92a6de25, and and copy the skill/mcd-event-radar/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-18: [FINGERPRINTS] - SKILL.md: SHA-256 28a06419f858354a4602622503ce69fd6de28ea0c08ebc7052cf5f068dd0b937 - scripts/check-connector.mjs: SHA-256 68498ed67a7b1013a9d5e70fc3879ea59f5eeca0d5bb56ae26f4a1323e90cb09 - scripts/lib/html-map.mjs: SHA-256 5ae4dfaa6e01c2351c30b8ae2d836a583f6d864ded339d0fcc078cf59f7cef0f - scripts/lib/mcp-client.mjs: SHA-256 59f0e0a0ac7c224b621b2fa89f0ccd08796cf5ec6c6f468fe7ad4ff281eecf5c - scripts/live.mjs: SHA-256 5d09e801058c693e8bd3bbae3db0f4a9fbdfebcc1a7ac041b0f04b074c9fd3ae - scripts/locate.mjs: SHA-256 8f15d9658415d3d243ed8f7207659162e56effc3cc84b1efd9965e14e3120834 - scripts/radar.mjs: SHA-256 199c9a8b04fe3e9e3527e4c716af394bcc1ebe8e58a0c9d783eaf9d8644bb9d6 - scripts/setup-connector.mjs: SHA-256 a2708bb6459e2261f3dc23e3931c0eccc876ddd26786fd19405767d386222fb3 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full (and every other file in the folder) and tell me in plain words: what the skill does when used, which services it connects to, whether it reads or sends any personal information or keys, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds SKILL.md and seven dependency free Node.js scripts under scripts/: setup-connector.mjs (one click connector setup), check-connector.mjs (connector health check), locate.mjs (city level location detection), live.mjs (a direct MCP query fallback that writes a normalised local JSON file), radar.mjs (turns that JSON into the HTML map, or Markdown or JSON lists), and scripts/lib/mcp-client.mjs plus scripts/lib/html-map.mjs. The rest of the repository (README, examples, images, a prebuilt zip and one line installers that fetch the unpinned main branch) is not part of this listing: this install uses only the pinned folder above. - At use time, event data goes only to the McDonald's China MCP server at https://mcp.mcd.cn (Streamable HTTP POST, Authorization: Bearer token): campaign-calendar for leads, mall-points-products with the official activity category ids, mall-product-detail, and the verification chain query-party-city, query-party-store, query-party-store-date and query-party-store-session, carrying product ids (spuId, skuId), city codes, store codes and dates, and returning store names, addresses and official latitude and longitude that the map plots. The setup and check scripts also connect to that same server (an initialize and tools/list handshake) to validate your token, without printing it. One optional step talks to third parties, and the SKILL.md gates it on your one line consent: when you ask for events near you without naming a city, scripts/locate.mjs calls https://ipinfo.io/json, falling back to https://api.ip.sb/geoip, so those two geolocation services receive your public IP address (that is how IP location works) and return a city level result, which must be confirmed by you before any search, is never turned into a precise location, and is never written into memory. The map itself is generated locally and calls no online map service. - Two things write, and both are disclosed here. First, configuration: on first setup, setup-connector.mjs writes the mcd-mcp entry, including your token as the Bearer header, into ~/.workbuddy/mcp.json on your machine (it backs the existing file up first, preserves other servers, and refuses to touch a file that is not valid JSON). Second, booking: party-order-create creates a real theme event order, and the SKILL.md allows it only when you explicitly ask to book after seeing and confirming the event, city, store, date, session, headcount and fee; if the fee unit cannot be verified it must not create the order, and any payment link and amount are handed to you to pay yourself. The skill must never call ordinary ordering, coupon claiming, points redemption or lottery tools. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. The listing and the token are free; you pay only a booking you confirm, on the official payment link. The fictional file examples/sample-events.json in the repository is demo data that the SKILL.md forbids presenting as a live result. 3. When I say "yes, install", install it as a skill: copy the whole folder into the agent's skills directory, in a folder named "mcd-event-radar", keeping every file (SKILL.md, scripts/check-connector.mjs, scripts/lib/html-map.mjs, scripts/lib/mcp-client.mjs, scripts/live.mjs, scripts/locate.mjs, scripts/radar.mjs, scripts/setup-connector.mjs). 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (for example: get the McDonald's China MCP token myself at https://open.mcd.cn/mcp with my mobile phone number if I do not have one, put it only in my own private MCP client configuration or environment variable and never paste it into a shared chat, install Python if it is missing, and set up the mcd-mcp connector to https://mcp.mcd.cn if it is not configured; using the skill is a separate step that only starts when I ask for it, and any order, coupon claim or booking happens only as disclosed above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.