Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Nothing to run from here
Tap2Cal 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.
96/100
trust score
9
tools declared
local
or remote
—
downloads a day
What it does
Turn events into shareable add-to-calendar links for Google, Apple and Outlook, with RSVPs.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'TAP2CAL_API_KEY=${TAP2CAL_API_KEY}' --transport stdio tap2cal-mcp '--' npx -y tap2cal-mcp
# 2 — ask your agent for something these tools do
# create_event, list_my_events, get_event and 6 more
It needs TAP2CAL_API_KEY: this reads it from your environment, so export it first.
Tap2Cal costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MAAll 2 servers
matthiasmaigner2 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. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads TAP2CAL_API_KEY (Your Tap2Cal API key from https://tap2cal.com/app/account) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx TAP2CAL_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'TAP2CAL_API_KEY=${TAP2CAL_API_KEY}' --transport stdio tap2cal-mcp '--' npx -y tap2cal-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Or connect to its publisher’s address
Its publisher also runs it at https://mcp.tap2cal.com: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http tap2cal-mcp https://mcp.tap2cal.comFree on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: TAP2CAL_API_KEY — Your Tap2Cal API key from https://tap2cal.com/app/account. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
9 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Creates a public page for an event with a shareable link. Anyone who opens the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Event name, up to 120 characters |
| startDate | string | yes | Start date as YYYY-MM-DD |
| endDate | string | no | End date as YYYY-MM-DD, defaults to the start date |
| startTime | string | no | Start time as HH:MM. Leave out for an all-day event |
| endTime | string | no | End time as HH:MM, required with a start time |
| timeZone | string | yes | IANA time zone, e.g. Europe/Vienna |
| location | string | no | Location, up to 200 characters |
| subtitle | string | no | Short subtitle, up to 160 characters |
| description | string | no | Description, up to 1000 characters |
| link | string | no | Related https link, e.g. tickets |
| accentColor | string | no | Button color as #rrggbb |
| backgroundColor | string | no | Page background color as #rrggbb |
| lang | string | no | Language of the link preview |
| rsvpEnabled | boolean | no | Let guests accept or decline with their name |
| slug | string | no | Own link, e.g. summer-party for tap2cal.com/summer-party. At least 3 characters. Leave out for a link made from the name |
Lists the events of this Tap2Cal account with their links, page views, calendar
No parameter schema on file.
Returns one event with all its details, its current link, earlier links that still
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event | string | yes | The event: its id, any of its links or the full URL |
Changes an event. Only the fields you pass change. Moving the start date without an
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event | string | yes | The event: its id, any of its links or the full URL |
| name | string | no | Event name, up to 120 characters |
| startDate | string | no | Start date as YYYY-MM-DD |
| endDate | string | no | End date as YYYY-MM-DD |
| startTime | yes | — | |
| endTime | yes | — | |
| timeZone | string | no | IANA time zone, e.g. Europe/Vienna |
| location | yes | — | |
| subtitle | yes | — | |
| description | yes | — | |
| link | yes | — | |
| accentColor | yes | — | |
| backgroundColor | yes | — | |
| lang | string | no | Language of the link preview |
| rsvpEnabled | boolean | no | Let guests accept or decline with their name |
| slug | string | no | New link, e.g. summer-party for tap2cal.com/summer-party. At least 3 characters, up to 5 new links per event |
Disables an earlier link of an event, so it shows that the link is no longer valid.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event | string | yes | The event: its id, any of its links or the full URL |
| link | string | yes | The earlier link to disable, e.g. summer-party-x7k2 or its full URL |
Lists the guests who accepted or declined an event, with the number of people each guest brings along.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event | string | yes | The event: its id, any of its links or the full URL |
Adds or replaces the flyer of an event. It is shown on the event page and in link
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event | string | yes | The event: its id, any of its links or the full URL |
| imagePath | string | no | Path of an image file on this computer |
| imageUrl | string | no | URL of an image to download |
Removes the flyer of an event. The page and link preview go back to the design without image.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event | string | yes | The event: its id, any of its links or the full URL |
Deletes an event with its page, all its links, its flyer and its RSVPs. The links
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event | string | yes | The event: its id, any of its links or the full URL |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 Tap2Cal 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: —
ATrust score 96 / 100
Release 1.0.0 · scanned 15 Nov 2026
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 score96
Findings0 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digest9b1059eee96081d73924002f03925716bc432fea6537fab97248bdd28835184a
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (9 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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 |
|---|---|---|
| create_event | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| list_my_events | no tags | |
| get_event | no tags | |
| update_event | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| disable_old_link | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| list_rsvps | no tags | |
| set_flyer | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| remove_flyer | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| delete_event | 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 digest9b1059eee96081d7
Scanned2026-11-15
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.0.0. Pin a release below and the command asks for exactly that one.
1.0.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 Tap2Cal 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.