london.taskman/home-services · v1.0.0 · finance-and-payments
TaskMan of London is healthy: it completed an MCP handshake in 1171 ms and exposes 20 tools.
Book London furniture assembly, wall mounting, handyman, electrical, and smart home jobs.
Endpoint: https://taskman.london/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 20 |
| Latency | 1171 ms |
| Last checked (UTC) | 2026-10-15T12:30:16.501Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-15T12:30:16.501Z | Healthy | 1171 |
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. |
check_service_area | Use when the user provides a London postcode or asks whether TaskMan covers their area. |
get_quote_estimate | Use when the user asks about likely cost, ballpark pricing, or whether a task needs a custom quote. |
check_availability | Use when the user asks about dates, timing, or whether a service can likely be booked soon. |
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. |
create_booking_request | Use when the user is ready to submit details for a real TaskMan of London booking request. |
get_booking_status | Use when the user already has a TaskMan booking request and wants an update. |
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. |
start_customer_verification | Use when an existing customer wants to verify identity (OTP or magic link) before assistant-led booking. |
verify_customer_otp | Use after sending an OTP challenge, to verify the one-time passcode and open a short-lived booking session. |
verify_magic_link_token | Use when the customer clicks a magic link and provides the token for verification. |
get_customer_profile | Use after verification to load scoped customer profile details from CRM for booking. |
list_customer_addresses | Use after verification to list saved addresses linked to the verified customer. |
list_service_types | Use after verification to show supported service types before collecting booking details. |
get_customer_availability | Use after verification to check availability for a verified customer at a selected saved address. |
start_booking_payment | Use after collecting booking details to create a Stripe checkout payment session before final booking submission. |
get_booking_payment_status | Use to check whether a booking payment session is pending, paid, failed, canceled, or expired before attempting booking creation. |
create_customer_booking | Use after verification, detail collection, and confirmed paid payment session to create a booking scoped to the verified customer. |
update_contact_note | Use to append an internal CRM note for the verified customer during or after booking. |
tag_contact | Use to add CRM tags to the verified customer for booking workflow tracking. |