Official MCP RegistryListed
beep.me
Find when public events happen and get email reminders before them, following moved matches.
First seen 3 Nov 2026. Evidence as of 15 Nov 2026.
6
Tools
From an anonymous probe
1
Source listings
Each with its own history
7
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| confirm_email | Switch the user's beep.me reminders on with the 6-digit code from beep.me's confirmation email, so they don't have to leave the chat to click its link. Only with a code the user has typed into the chat themselves: never guess one, never reuse a code from earlier. Pass the address the reminder was made with. Wrong codes are limited; after that, the link in the same email still works. | Changes data |
| follow_team | Sign the user up for an email reminder before EVERY upcoming match of a football team. Matches added or moved later are covered too, so the user never has to come back. Use it when the user says every match, all matches, whenever <team> plays, or follow <team>; for one match, use remind_me. Ask the user for their email address first (never guess it). A new address gets one confirmation email, and the reminders start once the user clicks the link in it. Every reminder has a link to stop following. Only for teams, never for personal appointments. When beep.me is connected with sign-in, leave email out: it is on at once, with no confirmation email. | Changes data |
| my_reminders | List the reminders on the signed-in user's beep.me account: each upcoming event with when its email arrives, and each team they follow. Use it when the user asks what beep.me reminds them about, and before stop_reminder to find the id. Needs the user signed in to beep.me. | Read-only |
| remind_me | Sign the user up for an email reminder before a public event that search_events returned, or for an email when a value beep.me reads crosses a line the user chose (a watch from search_events). Ask the user for their email address first (never guess it) and pass either the event id, or the watch's source with direction and value. A new address gets one confirmation email, and the reminder is switched on once the user clicks the link in it. Only for events and watches search_events returned, never for personal appointments. When beep.me is connected with sign-in, leave email out: it is on at once, with no confirmation email. | Changes data |
| search_events | Find when a public event happens: a match or fixture, a game or film release, a TV season premiere, a concert, a festival, a sale, a public deadline or holiday. Call it whenever the user asks when something people wait for will happen, or asks to be reminded or notified about it. Results come from beep.me's catalog of upcoming public events, each with an id, its date and a link. Also finds the values beep.me reads (water and air temperatures, pollen, fuel prices, snow, power prices: 'watches', with what the value is now), for «tell me when X is over or under Y». Not for personal appointments or private to-dos (dentist, meetings, birthdays): beep.me only tracks public events, so use the user's own calendar or reminders for those. | Read-only |
| stop_reminder | Stop one reminder on the signed-in user's beep.me account: an event by its event_id, or every match of a followed team by its follow_id, both from my_reminders. Only when the user asked to stop it. Needs the user signed in to beep.me. | Destructive |
Change history
- server instructions changed (+"beep.me is a help, not a guarantee: an email can come late or not at all." +"missing it would cost the user something (a deadline, a fine, a towed car), say so and suggest they keep their own reminder too. When")
- search_events: description changed (+"Also finds the values beep.me reads (water and air temperatures, pollen, fuel prices, snow, power prices: 'watches', with what the value is now), for «tell me when X is over or under Y».")
- remind_me: input schema changed (+direction, +every, +source, +value)
- remind_me: description changed (+"returned, or for an email when a value beep.me reads crosses a line the user chose (a watch from search_events)." +"either" +"id, or the watch's source with direction and value.")
- server instructions changed (+"no events and no watches," +"A search result's watches are values beep.me reads from their source on a schedule (a water temperature, a pollen level, a fuel price): tell the user what the value is now and offer «beep.me can email you when <name> is over/under <value>»; never promise when, the email comes at the first reading that crosses the line. To set one, call remind_me with the watch's source, direction and value (every true for every crossing) instead of an event_id." +"address, and a known one used without sign-in,")
- server instructions changed (+"A result with a watch field waits for a value, not a date; when watch.read is false, nobody reads that source yet, so say the reminder is a wish until beep.me starts watching it.")
- Listed (registry)
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| Official MCP Registry | me.beep/beep | 3 Nov 2026 | 15 Nov 2026 | 1 |