beep.me

endpoint

https://beep.me/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is beep.me live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is beep.me free to use?

Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.

What tools does beep.me have?

6 tools: remind_me, follow_team, confirm_email, stop_reminder, search_events, my_reminders.

Is beep.me safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• my_reminders auth-required 1h ago

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 lines copy
• remind_me unknown never probed

  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.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435

  {
    "type": "object",
    "required": [
      "event_id"
    ],
    "properties": {
      "email": {
        "type": "string",
        "description": "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."
      },
      "country": {
        "type": "string",
        "description": "Optional two-letter country code of the user."
      },
      "event_id": {
        "type": "integer",
        "description": "The id of an event search_events returned."
      },
      "language": {
        "type": "string",
        "description": "Language for the emails: 'no' for Norwegian, 'en' for English (default)."
      },
      "timezone": {
        "type": "string",
        "description": "Optional IANA time zone of the user, e.g. 'Europe/Oslo', so the email shows their local time."
      },
      "remind_before_minutes": {
        "type": "integer",
        "maximum": 10080,
        "minimum": 5,
        "description": "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."
      }
    },
    "additionalProperties": false
  }

  arguments 35 lines copy
• follow_team unknown never probed

  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.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637

  {
    "type": "object",
    "required": [
      "team"
    ],
    "properties": {
      "team": {
        "type": "string",
        "maxLength": 100,
        "minLength": 2,
        "description": "The team as people write it: 'Manchester United', 'Bodø/Glimt', 'Real Madrid'."
      },
      "email": {
        "type": "string",
        "description": "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."
      },
      "country": {
        "type": "string",
        "description": "Optional two-letter country code of the user."
      },
      "language": {
        "type": "string",
        "description": "Language for the emails: 'no' for Norwegian, 'en' for English (default)."
      },
      "timezone": {
        "type": "string",
        "description": "Optional IANA time zone of the user, e.g. 'Europe/Oslo', so the email shows their local time."
      },
      "remind_before_minutes": {
        "type": "integer",
        "maximum": 10080,
        "minimum": 5,
        "description": "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."
      }
    },
    "additionalProperties": false
  }

  arguments 37 lines copy
• confirm_email unknown never probed

  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.

  mcp-tool

  12345678910111213141516171819

  {
    "type": "object",
    "required": [
      "email",
      "code"
    ],
    "properties": {
      "code": {
        "type": "string",
        "pattern": "^\\s*\\d{3}\\s*\\d{3}\\s*$",
        "description": "The 6-digit code from the email, exactly as the user typed it."
      },
      "email": {
        "type": "string",
        "description": "The user's own email address, exactly as they gave it."
      }
    },
    "additionalProperties": false
  }

  arguments 19 lines copy
• stop_reminder unknown never probed

  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.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "properties": {
      "event_id": {
        "type": "integer",
        "description": "An event's id from my_reminders."
      },
      "follow_id": {
        "type": "integer",
        "description": "A followed team's follow_id from my_reminders."
      }
    },
    "additionalProperties": false
  }

  arguments 14 lines copy
• search_events unknown 1h ago

  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.

  mcp-tool

  1234567891011121314151617181920212223242526

  {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "default": 5,
        "maximum": 40,
        "minimum": 1,
        "description": "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": {
        "type": "string",
        "maxLength": 100,
        "minLength": 2,
        "description": "1-5 keywords naming the thing, as it is usually written: 'Arsenal Chelsea', 'Geminids', 'Avatar 3', 'Black Friday'. Not a sentence."
      },
      "country": {
        "type": "string",
        "description": "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."
      }
    },
    "additionalProperties": false
  }

  arguments 26 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.