TaskMan of London
REMOTE · TASKMAN.LONDON · SCANNED AUG 3
Book London furniture assembly, wall mounting, handyman, electrical, and smart home jobs.
Available components
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 →
Endpoint Security63
- 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 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 1193 tokens (~59/item across 20 items; 20 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · taskman.london
claude mcp add --transport http london-taskman-home-services https://taskman.london/mcp
[mcp_servers.london-taskman-home-services] url = "https://taskman.london/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"london-taskman-home-services": {
"type": "remote",
"url": "https://taskman.london/mcp",
"enabled": true
}
}
} openclaw mcp add london-taskman-home-services --url https://taskman.london/mcp --transport streamable-http
mcp_servers:
london-taskman-home-services:
url: "https://taskman.london/mcp" {
"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.
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.
- 3 Aug 26 +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.
- 1 Aug 26 +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.
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 28 Jul 26 +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.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 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 3 Aug 2026 · Probed https://taskman.london/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=taskman.london | CN=WE1,O=Google Trust Services,C=US | 24 Jul 2026 | 22 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 3d81eb981ad1b3990e903770b303d720 |
| SANs: taskman.london, *.taskman.london | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of taskman.london. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| london. | present | 9956, 17464 | 8, 8 | Verified |
| taskman.london. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://taskman.london/mcp | Verified | 200 | |
| http (plaintext) | http://taskman.london/mcp | HTTPS enforced | 301 | https://taskman.london/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.
check_availability ~61
Use when the user asks about dates, timing, or whether a service can likely be booked soon.
| Name | Type | Req | Description |
|---|---|---|---|
| postcode | string | yes | — |
| preferred_date | string | — | — |
| service_type | string | yes | — |
| time_preference | string | — | — |
No output schema declared.
No examples provided.
check_service_area ~41
Use when the user provides a London postcode or asks whether TaskMan covers their area.
| Name | Type | Req | Description |
|---|---|---|---|
| postcode | string | yes | — |
| service_type | string | — | — |
No output schema declared.
No examples provided.
create_booking_request ~124
Use when the user is ready to submit details for a real TaskMan of London booking request.
| Name | Type | Req | Description |
|---|---|---|---|
| consent_to_contact | boolean | yes | — |
| customer_name | string | yes | — |
| string | — | — | |
| idempotency_key | string | — | — |
| phone | string | yes | — |
| photos_url | string | — | — |
| postcode | string | yes | — |
| preferred_date | string | — | — |
| service_type | string | yes | — |
| source | string | — | — |
| task_summary | string | yes | — |
| time_preference | string | — | — |
No output schema declared.
No examples provided.
create_customer_booking ~124
Use after verification, detail collection, and confirmed paid payment session to create a booking scoped to the verified customer.
| Name | Type | Req | Description |
|---|---|---|---|
| address_id | string | — | — |
| consent_to_contact | boolean | — | — |
| contact_id | string | — | — |
| idempotency_key | string | — | — |
| payment_session_id | string | yes | — |
| photos_url | string | — | — |
| preferred_date | string | — | — |
| service_type | string | yes | — |
| session_token | string | yes | — |
| task_summary | string | yes | — |
| time_preference | string | — | — |
No output schema declared.
No examples provided.
find_services ~55
Use when the user needs help identifying which TaskMan of London service fits their job, especially for vague home-service requests in London.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | — | — |
| query | string | — | — |
| urgency | string | — | — |
No output schema declared.
No examples provided.
get_booking_payment_status ~51
Use to check whether a booking payment session is pending, paid, failed, canceled, or expired before attempting booking creation.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_session_id | string | yes | — |
| session_token | string | yes | — |
No output schema declared.
No examples provided.
get_booking_status ~48
Use when the user already has a TaskMan booking request and wants an update.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_request_id | string | yes | — |
| string | — | — | |
| phone | string | — | — |
No output schema declared.
No examples provided.
get_customer_availability ~67
Use after verification to check availability for a verified customer at a selected saved address.
| Name | Type | Req | Description |
|---|---|---|---|
| address_id | string | — | — |
| preferred_date | string | — | — |
| service_type | string | yes | — |
| session_token | string | yes | — |
| time_preference | string | — | — |
No output schema declared.
No examples provided.
get_customer_profile ~31
Use after verification to load scoped customer profile details from CRM for booking.
| Name | Type | Req | Description |
|---|---|---|---|
| session_token | string | yes | — |
No output schema declared.
No examples provided.
get_quote_estimate ~103
Use when the user asks about likely cost, ballpark pricing, or whether a task needs a custom quote.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | — | — |
| item_count | integer | — | — |
| item_type | string | — | — |
| photos_provided | boolean | — | — |
| postcode | string | — | — |
| preferred_date | string | — | — |
| service_type | string | yes | — |
| task_summary | string | yes | — |
| wall_type | string | — | — |
No output schema declared.
No examples provided.
list_customer_addresses ~30
Use after verification to list saved addresses linked to the verified customer.
| Name | Type | Req | Description |
|---|---|---|---|
| session_token | string | yes | — |
No output schema declared.
No examples provided.
list_service_types ~30
Use after verification to show supported service types before collecting booking details.
| Name | Type | Req | Description |
|---|---|---|---|
| session_token | string | yes | — |
No output schema declared.
No examples provided.
match_providers ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| area_postcode | string | yes | — |
| location_id | string | — | — |
| preferred_date | string | — | — |
| service_type | string | yes | — |
| urgency | string | yes | — |
No output schema declared.
No examples provided.
start_booking_payment ~83
Use after collecting booking details to create a Stripe checkout payment session before final booking submission.
| Name | Type | Req | Description |
|---|---|---|---|
| address_id | string | — | — |
| contact_id | string | — | — |
| deposit_amount_minor | integer | — | — |
| preferred_date | string | — | — |
| service_type | string | yes | — |
| session_token | string | yes | — |
| task_summary | string | yes | — |
No output schema declared.
No examples provided.
start_customer_verification ~55
Use when an existing customer wants to verify identity (OTP or magic link) before assistant-led booking.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_preference | string | — | — |
| identifier | string | yes | — |
| method_preference | string | — | — |
No output schema declared.
No examples provided.
start_trusted_phone_session ~46
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.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | — |
No output schema declared.
No examples provided.
tag_contact ~37
Use to add CRM tags to the verified customer for booking workflow tracking.
| Name | Type | Req | Description |
|---|---|---|---|
| session_token | string | yes | — |
| tags | array | yes | — |
No output schema declared.
No examples provided.
update_contact_note ~40
Use to append an internal CRM note for the verified customer during or after booking.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | — |
| session_token | string | yes | — |
No output schema declared.
No examples provided.
verify_customer_otp ~48
Use after sending an OTP challenge, to verify the one-time passcode and open a short-lived booking session.
| Name | Type | Req | Description |
|---|---|---|---|
| challenge_id | string | yes | — |
| otp_code | string | yes | — |
No output schema declared.
No examples provided.
verify_magic_link_token ~32
Use when the customer clicks a magic link and provides the token for verification.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | — |
No output schema declared.
No examples provided.