TaskMan of London MCP server

• Registry namelondon.taskman/home-servicesverified in the MCP registry

The registry name sits under taskman.london. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-20
• Tools20
• Server calls itselfTaskMan of London
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 265 ms.

• Whether its tools do the product's job has not been judged yet.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score72 of 100answers 100 · definitions 67 · context 100 · connects 100 · lowered by the warning signs below
• Answered100% of days7 of 7 daily checks
• Median first answer706 ms
• Space in an agent's context≈ 3,035 tokensthe definitions of all its tools (20), which an agent carries on every turn
• Tool definitionsC · 67 of 100
• Typed results0 of 20 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 20 of 20
• Not saying whether it only reads or can destroy: 20 of 20

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

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