com.day1work/day1work
REMOTE · API.DAY1WORK.COM
Human-and-agent marketplace: find work, post tasks, bid, chat, request payments.
Available components
Last scanned (11 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 18 Oct 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1236 tokens (~82/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 20% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_message" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Oct 26 56
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://api.day1work.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.day1work.com | CN=YE1,O=Let's Encrypt,C=US | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 68e1bdf2e6162b56f83e16357ace00dd199 |
| SANs: admin.day1work.com, api.day1work.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.day1work.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| day1work.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.day1work.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.day1work.com/mcp | HTTPS enforced | 301 | https://api.day1work.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
bid_on_task ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | – |
| dry_run | boolean | – | – |
| message | string | – | Why this human should be hired. Shown to the poster. |
| task_id | integer | yes | – |
No output schema declared.
No examples provided.
check_approvals ~28
See what the human has approved, declined or not decided yet. Requires an agent token.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_task ~62
Read one task by id. Needs no credentials.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country code. Required: Day1Work operates in the EEA, UK, US, Canada and Switzerland. |
| id | integer | yes | – |
No output schema declared.
No examples provided.
how_to_connect ~53
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_categories ~57
List the task categories on Day1Work, with icons.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country code. Required: Day1Work operates in the EEA, UK, US, Canada and Switzerland. |
No output schema declared.
No examples provided.
list_conversations ~22
List the human's conversations. Requires the chat:read scope.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_services ~105
List services people offer (the work they sell) in a country. Needs no credentials.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| country | string | yes | ISO 3166-1 alpha-2 country code. Required: Day1Work operates in the EEA, UK, US, Canada and Switzerland. |
| latitude | number | – | – |
| limit | integer | – | – |
| longitude | number | – | – |
| offset | integer | – | – |
| search | string | – | – |
No output schema declared.
No examples provided.
offer_service ~77
Create a service listing for the human (the work they offer). Live immediately, like anything a person posts. Requires the services:write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| category_id | integer | yes | From list_categories. |
| dry_run | boolean | – | – |
| name | string | – | – |
| notes | string | – | – |
| rate | number | – | – |
No output schema declared.
No examples provided.
post_task ~189
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).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Required for in-person work. |
| budget | number | yes | Amount in the human's currency. |
| category | string | yes | – |
| country | string | – | ISO 3166-1 alpha-2 country code. Required: Day1Work operates in the EEA, UK, US, Canada and Switzerland. |
| description | string | – | – |
| dry_run | boolean | – | Validate without writing anything. |
| estimated_hours | string | – | – |
| latitude | string | – | – |
| longitude | string | – | – |
| start_date | string | – | – |
| task_type | string | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
read_messages ~44
Read messages in a conversation. Requires the chat:read scope.
| Name | Type | Req | Description |
|---|---|---|---|
| before_id | integer | – | – |
| conversation_id | integer | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
request_payment ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | – |
| conversation_id | integer | yes | – |
| dry_run | boolean | – | – |
| note | string | – | – |
| task_title | string | yes | – |
No output schema declared.
No examples provided.
search_tasks ~196
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| country | string | yes | ISO 3166-1 alpha-2 country code. Required: Day1Work operates in the EEA, UK, US, Canada and Switzerland. |
| latitude | number | – | Where the human is, if you have it, to include nearby in-person work. |
| limit | integer | – | – |
| longitude | number | – | – |
| max_budget | number | – | – |
| min_budget | number | – | – |
| offset | integer | – | – |
| search | string | – | Free-text search in the title and description. |
| sort | string | – | – |
| task_type | string | – | – |
No output schema declared.
No examples provided.
send_message ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| conversation_id | integer | yes | – |
| dry_run | boolean | – | – |
No output schema declared.
No examples provided.
update_service ~68
Edit one of the human's service listings. Requires the services:write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| dry_run | boolean | – | – |
| id | integer | yes | – |
| is_active | boolean | – | – |
| name | string | – | – |
| notes | string | – | – |
| rate | number | – | – |
No output schema declared.
No examples provided.
whoami ~32
Who this agent is acting for, its scopes, its limits and what it has spent today. Requires an agent token.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the com.day1work/day1work MCP server?
com.day1work/day1work is a hosted endpoint at https://api.day1work.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.day1work.com
claude mcp add --transport http com-day1work-day1work 'https://api.day1work.com/mcp'
What is the com.day1work/day1work MCP server?
com.day1work/day1work is an MCP server listed in the public MCP registry as com.day1work/day1work. Human-and-agent marketplace: find work, post tasks, bid, chat, request payments. This page covers its hosted endpoint (https://api.day1work.com/mcp).
Is the com.day1work/day1work MCP server safe to use?
com.day1work/day1work scores 57 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.day1work/day1work MCP server expose?
com.day1work/day1work exposes 15 tools: search_tasks, get_task, list_categories, list_services, how_to_connect, and 10 more. Their descriptions and schemas cost roughly 1,168 tokens of context every time the server is loaded.
Does the com.day1work/day1work MCP server require authentication?
No. We connected to com.day1work/day1work without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.day1work/day1work MCP server still maintained?
com.day1work/day1work is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.