# TaskMan of London

- Registry name: `london.taskman/home-services` · version 1.0.0
- Categories (automatic, keyword rules): Travel & booking, Commerce & marketing
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): logging, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=london.taskman%2Fhome-services
- Server page: https://mcpstation.net/s/london.taskman--home-services.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://taskman.london/mcp`

## Tools (as reported by the server, not verified)

- `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.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html