# beep.me (remote · beep.me)

Find when public events happen and get email reminders before them, following moved matches.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `beep.me`: 63/100 (this document), [markdown](https://verifymcp.io/servers/me-beep-beep/beep.md), [page](https://verifymcp.io/servers/me-beep-beep/beep)

## Channel facts

- Endpoint: `https://beep.me/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (stop_reminder).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http me-beep-beep 'https://beep.me/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "me-beep-beep": {
      "url": "https://beep.me/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "me-beep-beep": {
      "type": "http",
      "url": "https://beep.me/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.me-beep-beep]
url = "https://beep.me/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "me-beep-beep": {
      "type": "remote",
      "url": "https://beep.me/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add me-beep-beep --url 'https://beep.me/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  me-beep-beep:
    url: "https://beep.me/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "me-beep-beep": {
      "Transport": "http",
      "Url": "https://beep.me/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add me-beep-beep -t streamable-http -u 'https://beep.me/mcp'
```

### Other

```json
{
  "mcpServers": {
    "me-beep-beep": {
      "type": "http",
      "url": "https://beep.me/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-03 (score 63)

First indexed and scored.

## MCP tools (6)

### `search_events` (~245 tokens)

Find when a public event happens

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.

Input parameters:

- `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, required): 1-5 keywords naming the thing, as it is usually written: 'Arsenal Chelsea', 'Geminids', 'Avatar 3', 'Black Friday'. Not a sentence.

### `remind_me` (~290 tokens)

Email me a reminder

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.

Input parameters:

- `country` (string): Optional two-letter country code of the user.
- `email` (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, required): 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.

### `follow_team` (~347 tokens)

Email me before every match of a 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.

Input parameters:

- `country` (string): Optional two-letter country code of the user.
- `email` (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, required): 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.

### `confirm_email` (~131 tokens)

Confirm my email with the code

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.

Input parameters:

- `code` (string, required): The 6-digit code from the email, exactly as the user typed it.
- `email` (string, required): The user's own email address, exactly as they gave it.

### `my_reminders` (~68 tokens)

List 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.

### `stop_reminder` (~97 tokens)

Stop a 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.

Input parameters:

- `event_id` (integer): An event's id from my_reminders.
- `follow_id` (integer): A followed team's follow_id from my_reminders.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/me-beep-beep/beep#diagnostics

## Score history

- 2026-11-04: 63
- 2026-11-03: 63

## Common questions

### 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.

## Links

- Remote endpoint: https://beep.me/mcp
- Website: https://beep.me/en/ai
- Changelog RSS feed: https://verifymcp.io/servers/me-beep-beep/beep.xml
- Changelog JSON feed: https://verifymcp.io/servers/me-beep-beep/beep.json
- HTML version of this page: https://verifymcp.io/servers/me-beep-beep/beep