Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Nothing to run from here
beep.me is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
6
tools declared
remote
at its publisher
—
calls last 7d
What it does
Find when public events happen and get email reminders before them, following moved matches.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http beep-me-mcp https://beep.me/mcp
# 2 — ask your agent for something these tools do
# search_events, remind_me, follow_team and 3 more
beep.me costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
BEAll 2 servers
beep2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http beep-me-mcp https://beep.me/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | no | 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 | no | 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. |
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 connect
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | no | Optional two-letter country code of the user. |
| string | no | 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 | no | Language for the emails: 'no' for Norwegian, 'en' for English (default). |
| remind_before_minutes | integer | no | 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 | no | Optional IANA time zone of the user, e.g. 'Europe/Oslo', so the email shows their local time. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | no | Optional two-letter country code of the user. |
| string | no | 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 | no | Language for the emails: 'no' for Norwegian, 'en' for English (default). |
| remind_before_minutes | integer | no | 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 | no | Optional IANA time zone of the user, e.g. 'Europe/Oslo', so the email shows their local time. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | integer | no | An event's id from my_reminders. |
| follow_id | integer | no | A followed team's follow_id from my_reminders. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install beep.me or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 0.4.0 · scanned 4 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestea2e15d632dc7f3b46adb3cde66dc17b883f41ceee6de51e06071dc811a48638
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_events | no tags | |
| remind_me | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| follow_team | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| confirm_email | state-write | state-write: declares readOnlyHint: false |
| my_reminders | no tags | |
| stop_reminder | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestea2e15d632dc7f3b
Scanned2026-11-04
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.4.0.
0.4.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish beep.me can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.