# TaskMan of London (remote · taskman.london)

Book London furniture assembly, wall mounting, handyman, electrical, and smart home jobs.

- Trust score: 63/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `taskman.london`: 63/100 (this document), [markdown](https://verifymcp.io/servers/london-taskman-home-services/taskman.md), [page](https://verifymcp.io/servers/london-taskman-home-services/taskman)

## Channel facts

- Endpoint: `https://taskman.london/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-08-03.

- **Endpoint Security**: 63/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 20 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.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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 1193 tokens (~59/item across 20 items; 20 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http london-taskman-home-services https://taskman.london/mcp
```

### Codex

```toml
[mcp_servers.london-taskman-home-services]
url = "https://taskman.london/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "london-taskman-home-services": {
      "type": "remote",
      "url": "https://taskman.london/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add london-taskman-home-services --url https://taskman.london/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  london-taskman-home-services:
    url: "https://taskman.london/mcp"
```

### Other

```json
{
  "mcpServers": {
    "london-taskman-home-services": {
      "type": "http",
      "url": "https://taskman.london/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-08-03 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 61, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 58, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 57, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 56, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 56)

First indexed and scored.

## MCP tools (20)

### `find_services` (~55 tokens)

Use when the user needs help identifying which TaskMan of London service fits their job, especially for vague home-service requests in London.

Input parameters:

- `area` (string)
- `query` (string)
- `urgency` (string)

### `check_service_area` (~41 tokens)

Use when the user provides a London postcode or asks whether TaskMan covers their area.

Input parameters:

- `postcode` (string, required)
- `service_type` (string)

### `get_quote_estimate` (~103 tokens)

Use when the user asks about likely cost, ballpark pricing, or whether a task needs a custom quote.

Input parameters:

- `brand` (string)
- `item_count` (integer)
- `item_type` (string)
- `photos_provided` (boolean)
- `postcode` (string)
- `preferred_date` (string)
- `service_type` (string, required)
- `task_summary` (string, required)
- `wall_type` (string)

### `check_availability` (~61 tokens)

Use when the user asks about dates, timing, or whether a service can likely be booked soon.

Input parameters:

- `postcode` (string, required)
- `preferred_date` (string)
- `service_type` (string, required)
- `time_preference` (string)

### `match_providers` (~87 tokens)

Use when an agent needs a single deterministic provider-matching result for assignment. Returns an ordered_candidates array sorted best-to-worst, where the first can_assign=true candidate is the assignee.

Input parameters:

- `area_postcode` (string, required)
- `location_id` (string)
- `preferred_date` (string)
- `service_type` (string, required)
- `urgency` (string, required)

### `create_booking_request` (~124 tokens)

Use when the user is ready to submit details for a real TaskMan of London booking request.

Input parameters:

- `consent_to_contact` (boolean, required)
- `customer_name` (string, required)
- `email` (string)
- `idempotency_key` (string)
- `phone` (string, required)
- `photos_url` (string)
- `postcode` (string, required)
- `preferred_date` (string)
- `service_type` (string, required)
- `source` (string)
- `task_summary` (string, required)
- `time_preference` (string)

### `get_booking_status` (~48 tokens)

Use when the user already has a TaskMan booking request and wants an update.

Input parameters:

- `booking_request_id` (string, required)
- `email` (string)
- `phone` (string)

### `start_trusted_phone_session` (~46 tokens)

Use in trusted telephony flows when the caller number is already verified by the channel provider and you need a short-lived booking session without OTP.

Input parameters:

- `identifier` (string, required)

### `start_customer_verification` (~55 tokens)

Use when an existing customer wants to verify identity (OTP or magic link) before assistant-led booking.

Input parameters:

- `channel_preference` (string)
- `identifier` (string, required)
- `method_preference` (string)

### `verify_customer_otp` (~48 tokens)

Use after sending an OTP challenge, to verify the one-time passcode and open a short-lived booking session.

Input parameters:

- `challenge_id` (string, required)
- `otp_code` (string, required)

### `verify_magic_link_token` (~32 tokens)

Use when the customer clicks a magic link and provides the token for verification.

Input parameters:

- `token` (string, required)

### `get_customer_profile` (~31 tokens)

Use after verification to load scoped customer profile details from CRM for booking.

Input parameters:

- `session_token` (string, required)

### `list_customer_addresses` (~30 tokens)

Use after verification to list saved addresses linked to the verified customer.

Input parameters:

- `session_token` (string, required)

### `list_service_types` (~30 tokens)

Use after verification to show supported service types before collecting booking details.

Input parameters:

- `session_token` (string, required)

### `get_customer_availability` (~67 tokens)

Use after verification to check availability for a verified customer at a selected saved address.

Input parameters:

- `address_id` (string)
- `preferred_date` (string)
- `service_type` (string, required)
- `session_token` (string, required)
- `time_preference` (string)

### `start_booking_payment` (~83 tokens)

Use after collecting booking details to create a Stripe checkout payment session before final booking submission.

Input parameters:

- `address_id` (string)
- `contact_id` (string)
- `deposit_amount_minor` (integer)
- `preferred_date` (string)
- `service_type` (string, required)
- `session_token` (string, required)
- `task_summary` (string, required)

### `get_booking_payment_status` (~51 tokens)

Use to check whether a booking payment session is pending, paid, failed, canceled, or expired before attempting booking creation.

Input parameters:

- `payment_session_id` (string, required)
- `session_token` (string, required)

### `create_customer_booking` (~124 tokens)

Use after verification, detail collection, and confirmed paid payment session to create a booking scoped to the verified customer.

Input parameters:

- `address_id` (string)
- `consent_to_contact` (boolean)
- `contact_id` (string)
- `idempotency_key` (string)
- `payment_session_id` (string, required)
- `photos_url` (string)
- `preferred_date` (string)
- `service_type` (string, required)
- `session_token` (string, required)
- `task_summary` (string, required)
- `time_preference` (string)

### `update_contact_note` (~40 tokens)

Use to append an internal CRM note for the verified customer during or after booking.

Input parameters:

- `note` (string, required)
- `session_token` (string, required)

### `tag_contact` (~37 tokens)

Use to add CRM tags to the verified customer for booking workflow tracking.

Input parameters:

- `session_token` (string, required)
- `tags` (array, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/london-taskman-home-services/taskman#diagnostics

## Score history

- 2026-08-03: 63
- 2026-08-02: 62
- 2026-08-01: 62
- 2026-07-31: 61
- 2026-07-30: 58
- 2026-07-29: 58
- 2026-07-28: 57
- 2026-07-27: 56
- 2026-07-26: 56

## Links

- Remote endpoint: https://taskman.london/mcp
- Website: https://taskman.london/mcp
- Changelog RSS feed: https://verifymcp.io/servers/london-taskman-home-services/taskman/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/london-taskman-home-services/taskman/changelog.json
- HTML version of this page: https://verifymcp.io/servers/london-taskman-home-services/taskman