TaskMan of London
REMOTE · TASKMAN.LONDON
Book London furniture assembly, wall mounting, handyman, electrical, and smart home jobs.
Available components
Last scanned (14 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 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 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 Usability68
- AI-judged instruction clarity (good).Pass
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation 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.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 7 Nov 26 +1
- Stability: 0.97 → pass security
- 6 Nov 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
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 21 Nov 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 | 19 Nov 2026 | 17 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 6ffe3a8acea159170eaf440e9e82d9db |
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of taskman.london. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| london. | DS published | 9956, 17464 | 8, 8 | Verified |
| taskman.london. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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. 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 →
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.
How do I install the TaskMan of London MCP server?
TaskMan of London is a hosted endpoint at https://taskman.london/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 · taskman.london
claude mcp add --transport http london-taskman-home-services 'https://taskman.london/mcp'
What is the TaskMan of London MCP server?
TaskMan of London is an MCP server listed in the public MCP registry as london.taskman/home-services. Book London furniture assembly, wall mounting, handyman, electrical, and smart home jobs. This page covers its hosted endpoint (https://taskman.london/mcp).
Is the TaskMan of London MCP server safe to use?
TaskMan of London scores 77 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 TaskMan of London MCP server expose?
TaskMan of London exposes 20 tools: find_services, check_service_area, get_quote_estimate, check_availability, match_providers, and 15 more. Their descriptions and schemas cost roughly 1,193 tokens of context every time the server is loaded.
Does the TaskMan of London MCP server require authentication?
No. We connected to TaskMan of London without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TaskMan of London MCP server still maintained?
TaskMan of London is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the TaskMan of London MCP server?
VerifyMCP ran 12 checks on TaskMan of London, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about TaskMan of London: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.