A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
Google Tasks 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.
97/100
trust score
3
downloads a day
local
runs on your machine
308
downloads in 30d
What it does
MCP server for Google Tasks API
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user google-tasks-mcp '--' npx -y @sargonpiraev/google-tasks-mcp-server
# 2 — ask your agent for something these tools do
# list-task-lists, insert-task-list, get-task-list and 11 more
Google Tasks costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SAAll 3 servers
sargonpiraev3 servers
3 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 runs on your machine: your client starts Google Tasks as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
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. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user google-tasks-mcp '--' npx -y @sargonpiraev/google-tasks-mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
Free 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 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
14 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.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
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 Google Tasks 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 97 / 100
Release 0.5.0 · scanned 14 Oct 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 score97
Findings0 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationsource
Surface digestbe279ae55cba26e02f6df9de80a2339d0c97104e779409c7e84ff250e355c079
Score vectorthreat 100 → client 97
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| 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 (14 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 |
|---|---|---|
| list-task-lists | no tags | |
| insert-task-list | external-sink | external-sink: handler sends an HTTP POST (apiClient.request({ headers: bearer ? { Authorization: Bearer ${bearer} } : undefined, m…) at build/server.js:95 |
| get-task-list | no tags | |
| update-task-list | external-sink | external-sink: handler sends an HTTP PUT (apiClient.request({ headers: bearer ? { Authorization: Bearer ${bearer} } : undefined, m…) at build/server.js:144 |
| patch-task-list | external-sink | external-sink: handler sends an HTTP PATCH (apiClient.request({ headers: bearer ? { Authorization: Bearer ${bearer} } : undefined, m…) at build/server.js:169 |
| delete-task-list | external-sink | external-sink: handler sends an HTTP DELETE (apiClient.request({ headers: bearer ? { Authorization: Bearer ${bearer} } : undefined, m…) at build/server.js:193 |
| list-tasks | no tags | |
| insert-task | external-sink | external-sink: handler sends an HTTP POST (apiClient.request({ headers: bearer ? { Authorization: Bearer ${bearer} } : undefined, m…) at build/server.js:255 |
| get-task | no tags | |
| update-task | external-sink | external-sink: handler sends an HTTP PUT (apiClient.request({ headers: bearer ? { Authorization: Bearer ${bearer} } : undefined, m…) at build/server.js:306 |
| patch-task | external-sink | external-sink: handler sends an HTTP PATCH (apiClient.request({ headers: bearer ? { Authorization: Bearer ${bearer} } : undefined, m…) at build/server.js:332 |
| delete-task | external-sink | external-sink: handler sends an HTTP DELETE (apiClient.request({ headers: bearer ? { Authorization: Bearer ${bearer} } : undefined, m…) at build/server.js:357 |
| move-task | external-sink | external-sink: handler sends an HTTP POST (apiClient.request({ headers: bearer ? { Authorization: Bearer ${bearer} } : undefined, m…) at build/server.js:385 |
| clear-tasks | external-sink | external-sink: handler sends an HTTP POST (apiClient.request({ headers: bearer ? { Authorization: Bearer ${bearer} } : undefined, m…) at build/server.js:409 |
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 digestbe279ae55cba26e0
Scanned2026-10-14
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 0.5.0. Pin a release below and the command asks for exactly that one.
0.5.0
20 Sep 2026
latestNo release note was published with this version.
0.4.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
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 Google Tasks 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.