TaskMan of London

Name: TaskMan of London
Author: london.taskman

MCP serverMCP

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

by london.taskmanhomepage ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"taskman-of-london","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability4/4 checks ok

30 days ago

when	check	result	http	latency	detail
16 min ago	mcp initialize	ok	200	206 ms	server TaskMan of London 1.0.0 · protocol 2025-06-18 · 20 tools
7 h ago	mcp initialize	ok	200	145 ms	server TaskMan of London 1.0.0 · protocol 2025-06-18 · 20 tools
14 h ago	mcp initialize	ok	200	159 ms	server TaskMan of London 1.0.0 · protocol 2025-06-18 · 20 tools
21 h ago	mcp initialize	ok	200	134 ms	server TaskMan of London 1.0.0 · protocol 2025-06-18 · 20 tools
28 h ago	mcp initialize	ok	200	132 ms	server TaskMan of London 1.0.0 · protocol 2025-06-18 · 20 tools

Tools observed via MCP handshake

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

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrylondon.taskman/home-services

first seen 29 h ago · fetched 29 h agoopen ↗

Field history (6 recent events)

29 h ago · declared · summary → "Book London furniture assembly, wall mounting, handyman, electrical, and smart home jobs."
29 h ago · declared · description → "Book London furniture assembly, wall mounting, handyman, electrical, and smart home jobs."
29 h ago · declared · publisherName → "london.taskman"
29 h ago · declared · homepageUrl → "https://taskman.london/mcp"
29 h ago · declared · version → "1.0.0"
29 h ago · declared · protocols → ["mcp"]

TaskMan of London

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from