beep.me
REMOTE · BEEP.ME
Find when public events happen and get email reminders before them, following moved matches.
Available components
Last scanned (22 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Productivity and Notes
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (stop_reminder). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1460 tokens (~243/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://beep.me/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=beep.me | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 14 Jul 2026 | 14 Jan 2027 | RSA 2048 | SHA256-RSA | 8a73c5c70747adfa4c0308d99fb08ee |
| SANs: beep.me | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of beep.me. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| me. | present | 45352 | 8 | Verified |
| beep.me. | present | 12362, 12362 | 15, 15 | Verified |
| beep.me. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://beep.me/mcp | Verified | 200 | |
| http (plaintext) | http://beep.me/mcp | HTTPS enforced | 301 | https://beep.me/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
confirm_email Confirm my email with the code ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The 6-digit code from the email, exactly as the user typed it. |
| string | yes | The user's own email address, exactly as they gave it. |
No output schema declared.
No examples provided.
follow_team Email me before every match of a team ~347
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional two-letter country code of the user. |
| string | – | The user's own email address, exactly as they gave it. Leave it out when beep.me is connected with sign-in: the signed-in account's own address is used. | |
| language | string | – | Language for the emails: 'no' for Norwegian, 'en' for English (default). |
| remind_before_minutes | integer | – | Optional. How many minutes before the start the email should arrive, when the user said so: 30 for «half an hour before», 1440 for «a day before». Leave it out to use the event's own time. |
| team | string | yes | The team as people write it: 'Manchester United', 'Bodø/Glimt', 'Real Madrid'. |
| timezone | string | – | Optional IANA time zone of the user, e.g. 'Europe/Oslo', so the email shows their local time. |
No output schema declared.
No examples provided.
my_reminders List my reminders ~68
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
remind_me Email me a reminder ~290
Sign the user up for an email reminder before a public event that search_events returned. Ask the user for their email address first (never guess it) and pass the event id from search_events. A new address gets one confirmation email, and the reminder is switched on once the user clicks the link in it. Only for events 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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional two-letter country code of the user. |
| string | – | The user's own email address, exactly as they gave it. Leave it out when beep.me is connected with sign-in: the signed-in account's own address is used. | |
| event_id | integer | yes | The id of an event search_events returned. |
| language | string | – | Language for the emails: 'no' for Norwegian, 'en' for English (default). |
| remind_before_minutes | integer | – | Optional. How many minutes before the start the email should arrive, when the user said so: 30 for «half an hour before», 1440 for «a day before». Leave it out to use the event's own time. |
| timezone | string | – | Optional IANA time zone of the user, e.g. 'Europe/Oslo', so the email shows their local time. |
No output schema declared.
No examples provided.
search_events Find when a public event happens ~245
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. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional two-letter country code of the user (NO, GB, US…). Local events rank first, and another country's holidays and deadlines are left out. |
| limit | integer | – | How many events, soonest first. Raise it to see a whole season, e.g. to find which of a team's matches are away in Spain. |
| query | string | yes | 1-5 keywords naming the thing, as it is usually written: 'Arsenal Chelsea', 'Geminids', 'Avatar 3', 'Black Friday'. Not a sentence. |
No output schema declared.
No examples provided.
stop_reminder Stop a reminder ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | integer | – | An event's id from my_reminders. |
| follow_id | integer | – | A followed team's follow_id from my_reminders. |
No output schema declared.
No examples provided.
How do I install the beep.me MCP server?
beep.me is a hosted endpoint at https://beep.me/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · beep.me
claude mcp add --transport http me-beep-beep 'https://beep.me/mcp'
What is the beep.me MCP server?
beep.me is an MCP server listed in the public MCP registry as me.beep/beep. Find when public events happen and get email reminders before them, following moved matches. This page covers its hosted endpoint (https://beep.me/mcp).
Is the beep.me MCP server safe to use?
beep.me scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the beep.me MCP server expose?
beep.me exposes 6 tools: search_events, remind_me, follow_team, confirm_email, my_reminders, stop_reminder. Their descriptions and schemas cost roughly 1,178 tokens of context every time the server is loaded.
Does the beep.me MCP server require authentication?
No. We connected to beep.me without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the beep.me MCP server still maintained?
beep.me is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.