← Registry

Collaboration

day1work.com

MCP server for Day1Work that lets agents search tasks and services, read task details, list categories, and learn how to connect to humans via device-flow approval.

1 endpoint15 known toolsFirst detected October 18, 2026Last detected October 18, 2026

ENDPOINT 1

https://api.day1work.com/mcp

No auth detected

MCP server metadata

Name
day1work
Version
1.0.0
Capabilities
tools
Server instructions

Day1Work is a human-and-agent marketplace across the EEA, UK, US, Canada and Switzerland. Search tasks and services without credentials. To act for a human (post tasks or services, bid, chat, request payments) connect with the device flow via how_to_connect. Money always needs the human's approval.

Known tools 15

search_tasks

Search open tasks on Day1Work.

Inferred read-only
get_task

Read one task by id.

Inferred read-only
list_categories

List the task categories on Day1Work, with icons.

Inferred read-only
list_services

List services people offer (the work they sell) in a country.

Inferred read-only
how_to_connect

Explain how to connect an agent to a human on Day1Work: the device flow, the scopes, and what needs the human's approval.

Inferred read-only
whoami

Who this agent is acting for, its scopes, its limits and what it has spent today.

Inferred read-only
post_task

Post a task for the human.

Potential side effects
offer_service

Create a service listing for the human (the work they offer).

Potential side effects
update_service

Edit one of the human's service listings.

Potential side effects
bid_on_task

Bid on a task for the human, with an optional short pitch.

Inferred read-only
list_conversations

List the human's conversations.

Inferred read-only
read_messages

Read messages in a conversation.

Inferred read-only
send_message

Send a chat message for the human.

Potential side effects
request_payment

Ask the human to approve a payment request in a conversation.

Potential side effects
check_approvals

See what the human has approved, declined or not decided yet.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.day1work]
url = "https://api.day1work.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "day1work": {
      "type": "http",
      "url": "https://api.day1work.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: day1work
Remote MCP URL: https://api.day1work.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "day1work": {
      "url": "https://api.day1work.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "day1work": {
      "type": "http",
      "url": "https://api.day1work.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "day1work",
  "transport": "streamable-http",
  "url": "https://api.day1work.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for day1work.com was fetched 2026-10-22T00:29:29.785Z.

Trust status Neutral

day1work.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.