Connect TaskMan of London and your agent gets 20 tools, among them check_availability, check_service_area, create_booking_request. It answers at https://taskman.london/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.
Book London furniture assembly, wall mounting, handyman, electrical, and smart home jobs.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
check_availability | Use when the user asks about dates, timing, or whether a service can likely be booked soon. Inputs: service_type, postcode, preferred_date, time_preference |
check_service_area | Use when the user provides a London postcode or asks whether TaskMan covers their area. Inputs: postcode, service_type |
create_booking_request | Use when the user is ready to submit details for a real TaskMan of London booking request. Inputs: customer_name, phone, email, postcode, service_type, task_summary |
create_customer_booking | Use after verification, detail collection, and confirmed paid payment session to create a booking scoped to the verified customer. Inputs: session_token, contact_id, service_type, task_summary, payment_session_id, idempotency_key |
find_services | Use when the user needs help identifying which TaskMan of London service fits their job, especially for vague home-service requests in London. Inputs: query, area, urgency |
get_booking_payment_status | Use to check whether a booking payment session is pending, paid, failed, canceled, or expired before attempting booking creation. Inputs: session_token, payment_session_id |
get_booking_status | Use when the user already has a TaskMan booking request and wants an update. Inputs: booking_request_id, phone, email |
get_customer_availability | Use after verification to check availability for a verified customer at a selected saved address. Inputs: session_token, service_type, address_id, preferred_date, time_preference |
get_customer_profile | Use after verification to load scoped customer profile details from CRM for booking. Inputs: session_token |
get_quote_estimate | Use when the user asks about likely cost, ballpark pricing, or whether a task needs a custom quote. Inputs: service_type, task_summary, item_count, item_type, brand, wall_type |
list_customer_addresses | Use after verification to list saved addresses linked to the verified customer. Inputs: session_token |
list_service_types | Use after verification to show supported service types before collecting booking details. Inputs: session_token |
match_providers | 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. Inputs: service_type, area_postcode, urgency, preferred_date, location_id |
start_booking_payment | Use after collecting booking details to create a Stripe checkout payment session before final booking submission. Inputs: session_token, contact_id, service_type, task_summary, preferred_date, address_id |
start_customer_verification | Use when an existing customer wants to verify identity (OTP or magic link) before assistant-led booking. Inputs: identifier, method_preference, channel_preference |
start_trusted_phone_session | 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. Inputs: identifier |
tag_contact | Use to add CRM tags to the verified customer for booking workflow tracking. Inputs: session_token, tags |
update_contact_note | Use to append an internal CRM note for the verified customer during or after booking. Inputs: session_token, note |
verify_customer_otp | Use after sending an OTP challenge, to verify the one-time passcode and open a short-lived booking session. Inputs: challenge_id, otp_code |
verify_magic_link_token | Use when the customer clicks a magic link and provides the token for verification. Inputs: token |
Every block below points at https://taskman.london/mcp. Pick your client and copy.
claude mcp add --transport http taskman-of-london https://taskman.london/mcp
{
"mcpServers": {
"taskman-of-london": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://taskman.london/mcp"]
}
}
}{
"mcpServers": {
"taskman-of-london": {
"url": "https://taskman.london/mcp"
}
}
}{
"servers": {
"taskman-of-london": {
"type": "http",
"url": "https://taskman.london/mcp"
}
}
}{
"context_servers": {
"taskman-of-london": {
"url": "https://taskman.london/mcp"
}
}
}{
"mcpServers": {
"taskman-of-london": {
"serverUrl": "https://taskman.london/mcp"
}
}
}{
"mcpServers": {
"taskman-of-london": {
"url": "https://taskman.london/mcp"
}
}
}name: TaskMan of London
version: 0.0.1
schema: v1
mcpServers:
- name: TaskMan of London
type: streamable-http
url: https://taskman.london/mcp{
"mcpServers": {
"taskman-of-london": {
"httpUrl": "https://taskman.london/mcp"
}
}
}{
"mcpServers": {
"taskman-of-london": {
"type": "http",
"url": "https://taskman.london/mcp"
}
}
}{
"mcpServers": {
"taskman-of-london": {
"url": "https://taskman.london/mcp"
}
}
}goose://extension?url=https%3A%2F%2Ftaskman.london%2Fmcp&type=streamable_http&id=taskman-of-london&name=TaskMan%20of%20London
It answered our last check on 24 October 2026 in 264 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by taskman.london and served from taskman.london, the vendor's own domain: https://taskman.london/mcp.
20, as returned by the server's own tools/list on 22 September 2026: check_availability, check_service_area, create_booking_request, create_customer_booking, find_services, get_booking_payment_status, get_booking_status, get_customer_availability, and 12 more.
It answered our last check on 24 October 2026 in 264 ms. Over 6 checks since 12 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://taskman.london/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: london.taskman. Endpoint host: taskman.london. ARD identifier: urn:air:london.taskman:mcp:home-services.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.