A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
Day1work 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
15
tools declared
remote
at its publisher
—
calls last 7d
What it does
Human-and-agent marketplace: find work, post tasks, bid, chat, request payments.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http day1work-mcp https://api.day1work.com/mcp
# 2 — ask your agent for something these tools do
# search_tasks, get_task, list_categories and 12 more
Day1work costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DAAll 1 server
day1work1 server
1 category
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 day1work-mcp https://api.day1work.com/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
15 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.
Search open tasks on Day1Work. Reading needs no credentials. Country is a hard boundary: no listing crosses a border. In-person tasks are returned only when you pass latitude and longitude, and only within that country's radius. Addresses are approximate and posters are not identified.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country code. Required: Day1Work operates in the EEA, UK, US, Canada and Switzerland. |
| latitude | number | no | Where the human is, if you have it, to include nearby in-person work. |
| longitude | number | no | — |
| category | string | no | — |
| search | string | no | Free-text search in the title and description. |
| task_type | string | no | — |
| min_budget | number | no | — |
| max_budget | number | no | — |
| sort | string | no | — |
| limit | integer | no | — |
| offset | integer | no | — |
Read one task by id. Needs no credentials.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | — |
| country | string | yes | ISO 3166-1 alpha-2 country code. Required: Day1Work operates in the EEA, UK, US, Canada and Switzerland. |
List the task categories on Day1Work, with icons.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country code. Required: Day1Work operates in the EEA, UK, US, Canada and Switzerland. |
List services people offer (the work they sell) in a country. Needs no credentials.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country code. Required: Day1Work operates in the EEA, UK, US, Canada and Switzerland. |
| latitude | number | no | — |
| longitude | number | no | — |
| category | string | no | — |
| search | string | no | — |
| limit | integer | no | — |
| offset | integer | no | — |
Explain how to connect an agent to a human on Day1Work: the device flow, the scopes, and what needs the human's approval. Call this when you need to act for someone but have no token yet.
No parameter schema on file.
Who this agent is acting for, its scopes, its limits and what it has spent today. Requires an agent token.
No parameter schema on file.
Post a task for the human. It goes live immediately, exactly like a task a person posts in the app. Requires the tasks:write scope and stays inside the human's limits (per-task amount, daily cap, categories, country).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | — |
| description | string | no | — |
| category | string | yes | — |
| task_type | string | no | — |
| budget | number | yes | Amount in the human's currency. |
| address | string | no | Required for in-person work. |
| latitude | string | no | — |
| longitude | string | no | — |
| country | string | no | ISO 3166-1 alpha-2 country code. Required: Day1Work operates in the EEA, UK, US, Canada and Switzerland. |
| start_date | string | no | — |
| estimated_hours | string | no | — |
| dry_run | boolean | no | Validate without writing anything. |
Create a service listing for the human (the work they offer). Live immediately, like anything a person posts. Requires the services:write scope.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category_id | integer | yes | From list_categories. |
| name | string | no | — |
| rate | number | no | — |
| notes | string | no | — |
| dry_run | boolean | no | — |
Edit one of the human's service listings. Requires the services:write scope.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | — |
| name | string | no | — |
| rate | number | no | — |
| notes | string | no | — |
| is_active | boolean | no | — |
| dry_run | boolean | no | — |
Bid on a task for the human, with an optional short pitch. Requires the bids:write scope. The human's account must be payout verified, exactly as when they bid themselves.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | integer | yes | — |
| amount | number | yes | — |
| message | string | no | Why this human should be hired. Shown to the poster. |
| dry_run | boolean | no | — |
List the human's conversations. Requires the chat:read scope.
No parameter schema on file.
Read messages in a conversation. Requires the chat:read scope.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| conversation_id | integer | yes | — |
| limit | integer | no | — |
| before_id | integer | no | — |
Send a chat message for the human. It is labelled as coming from an AI agent, so the other person always knows. Requires the chat:write scope.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| conversation_id | integer | yes | — |
| content | string | yes | — |
| dry_run | boolean | no | — |
Ask the human to approve a payment request in a conversation. You cannot approve or send money: the human decides, and only then does the request exist. Requires the payments:request scope.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| conversation_id | integer | yes | — |
| task_title | string | yes | — |
| amount | number | yes | — |
| note | string | no | — |
| dry_run | boolean | no | — |
See what the human has approved, declined or not decided yet. Requires an agent token.
No parameter schema on file.
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 Day1work 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 1.0.0 · scanned 20 Oct 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 · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest128bfc3227a61f0dac2f3d5d58755c6c161e9d61fd8fc684aa3eef14cbbac841
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_tasks | no tags | |
| get_task | no tags | |
| list_categories | no tags | |
| list_services | no tags | |
| how_to_connect | no tags | |
| whoami | no tags | |
| post_task | state-write | state-write: declares readOnlyHint: false |
| offer_service | state-write | state-write: declares readOnlyHint: false |
| update_service | state-write | state-write: declares readOnlyHint: false |
| bid_on_task | state-write | state-write: declares readOnlyHint: false |
| list_conversations | state-write | state-write: declares readOnlyHint: false |
| read_messages | untrusted-inputstate-write | untrusted-input: keyword "read_message"; state-write: declares readOnlyHint: false |
| send_message | external-sinkstate-write | external-sink: keyword "send_message"; state-write: declares readOnlyHint: false |
| request_payment | state-write | state-write: declares readOnlyHint: false |
| check_approvals | no tags |
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.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest128bfc3227a61f0d
Scanned2026-10-20
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 1.0.0.
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 Day1work 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.