Skip to content

beep.me MCP server

me.beep/beepbeep.mestreamable-httpv0.4.0Scanned

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

6 tools: 1 can delete or cancel things, 3 change things and 2 only read.

Tools: 1 delete, 0 irreversible, 3 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the beep.me MCP server can do

The beep.me MCP server is published by beep.me, a domain the MCP Registry verified. It has 6 tools. It can delete or cancel things (1 tool: stop_reminder) and create or change data (3 tools: remind_me, follow_team and confirm_email). 2 tools only read.

1 tool reads private data (my_reminders); 3 tools bring in text other people can write (remind_me, follow_team and my_reminders).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 16, 2026, version 0.4.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Deletes or cancels 1Claude Code: deny
  • stop_reminderStop 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.No findings

    Why it is in this group

    • The name "stop_reminder" says "stop": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
Changes things 3Claude Code: ask
  • confirm_emailSwitch 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.No findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
  • follow_teamSign the user up for an email reminder before EVERY upcoming match of a football team.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: false
  • remind_meSign 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 sea…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: false
Only reads 2Show 2 read-only tools
  • my_remindersList the reminders on the signed-in user's beep.me account: each upcoming event with when its email arrives, and each team they follow.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • search_eventsFind 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.No findings

    Why it is in this group

    • The name "search_events" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:23 UTC, unchanged since Nov 4, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://beep.me/.well-known/oauth-protected-resource/mcp
Authorization servers
https://beep.me
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://beep.me/mcp: tools/list returned 6 tools to an anonymous client, including stop_reminder (destructive), remind_me (write), follow_team (write), confirm_email (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff

Install

Pinned to version 0.4.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__beep__search_events",
      "mcp__beep__my_reminders"
    ],
    "ask": [
      "mcp__beep__remind_me",
      "mcp__beep__follow_team",
      "mcp__beep__confirm_email"
    ],
    "deny": [
      "mcp__beep__stop_reminder"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as beep. Review it before you use it.

Capability tags behind 3 rules
  • mcp__beep__remind_me untrusted-input
  • mcp__beep__follow_team untrusted-input
  • mcp__beep__my_reminders private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/me.beep/beep/verify?hash=e03c7d35bb7b557b3c8b5c9f1dd14f22b9055f21c623380b03ad9365e7c7e3d5" | jq -e '.changed == false'

Pinned hash e03c7d35bb7b, from Nov 16, 2026, 20:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/me.beep/beep/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for me.beep/beep
[![Anlyon Radar](https://radar.anlyon.com/badge/me.beep/beep.svg)](https://radar.anlyon.com/servers/me.beep/beep)

Source: MCP Registry. Synced Nov 3, 2026, 09:18 UTC.

beep.me MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the beep.me MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the beep.me MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: stop_reminder.

Can the beep.me MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the beep.me MCP server have?

6 tools: 1 destructive, 3 write, 2 read. stop_reminder, remind_me, follow_team, confirm_email, search_events and my_reminders.

Does the beep.me MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the beep.me MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the beep.me MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.