# com.day1work/day1work (remote · api.day1work.com)

Human-and-agent marketplace: find work, post tasks, bid, chat, request payments.

- Trust score: 57/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `api.day1work.com`: 57/100 (this document), [markdown](https://verifymcp.io/servers/com-day1work-day1work/api.md), [page](https://verifymcp.io/servers/com-day1work-day1work/api)

## Channel facts

- Endpoint: `https://api.day1work.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 1236 tokens (~82/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 73/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 20% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-day1work-day1work 'https://api.day1work.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-day1work-day1work": {
      "url": "https://api.day1work.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-day1work-day1work": {
      "type": "http",
      "url": "https://api.day1work.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-day1work-day1work]
url = "https://api.day1work.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-day1work-day1work": {
      "type": "remote",
      "url": "https://api.day1work.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-day1work-day1work --url 'https://api.day1work.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-day1work-day1work:
    url: "https://api.day1work.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-day1work-day1work": {
      "Transport": "http",
      "Url": "https://api.day1work.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-day1work-day1work -t streamable-http -u 'https://api.day1work.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-day1work-day1work": {
      "type": "http",
      "url": "https://api.day1work.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-18 (score 57, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-17 (score 56)

First indexed and scored.

## MCP tools (15)

### `search_tasks` (~196 tokens)

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.

Input parameters:

- `category` (string)
- `country` (string, required): 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)

### `get_task` (~62 tokens)

Read one task by id. Needs no credentials.

Input parameters:

- `country` (string, required): ISO 3166-1 alpha-2 country code. Required: Day1Work operates in the EEA, UK, US, Canada and Switzerland.
- `id` (integer, required)

### `list_categories` (~57 tokens)

List the task categories on Day1Work, with icons.

Input parameters:

- `country` (string, required): ISO 3166-1 alpha-2 country code. Required: Day1Work operates in the EEA, UK, US, Canada and Switzerland.

### `list_services` (~105 tokens)

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

Input parameters:

- `category` (string)
- `country` (string, required): 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)

### `how_to_connect` (~53 tokens)

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.

### `whoami` (~32 tokens)

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

### `post_task` (~189 tokens)

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).

Input parameters:

- `address` (string): Required for in-person work.
- `budget` (number, required): Amount in the human's currency.
- `category` (string, required)
- `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, required)

### `offer_service` (~77 tokens)

Create a service listing for the human (the work they offer). Live immediately, like anything a person posts. Requires the services:write scope.

Input parameters:

- `category_id` (integer, required): From list_categories.
- `dry_run` (boolean)
- `name` (string)
- `notes` (string)
- `rate` (number)

### `update_service` (~68 tokens)

Edit one of the human's service listings. Requires the services:write scope.

Input parameters:

- `dry_run` (boolean)
- `id` (integer, required)
- `is_active` (boolean)
- `name` (string)
- `notes` (string)
- `rate` (number)

### `bid_on_task` (~88 tokens)

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.

Input parameters:

- `amount` (number, required)
- `dry_run` (boolean)
- `message` (string): Why this human should be hired. Shown to the poster.
- `task_id` (integer, required)

### `list_conversations` (~22 tokens)

List the human's conversations. Requires the chat:read scope.

### `read_messages` (~44 tokens)

Read messages in a conversation. Requires the chat:read scope.

Input parameters:

- `before_id` (integer)
- `conversation_id` (integer, required)
- `limit` (integer)

### `send_message` (~63 tokens)

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.

Input parameters:

- `content` (string, required)
- `conversation_id` (integer, required)
- `dry_run` (boolean)

### `request_payment` (~84 tokens)

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.

Input parameters:

- `amount` (number, required)
- `conversation_id` (integer, required)
- `dry_run` (boolean)
- `note` (string)
- `task_title` (string, required)

### `check_approvals` (~28 tokens)

See what the human has approved, declined or not decided yet. Requires an agent token.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-day1work-day1work/api#diagnostics

## Score history

- 2026-10-18: 57
- 2026-10-17: 56

## Common questions

### 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.

## Links

- Remote endpoint: https://api.day1work.com/mcp
- Repository: https://github.com/MtechUAB/Day1Work
- Website: https://day1work.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-day1work-day1work/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-day1work-day1work/api.json
- HTML version of this page: https://verifymcp.io/servers/com-day1work-day1work/api