# london.taskman/home-services Book London furniture assembly, wall mounting, handyman, electrical, and smart home jobs. - **Type:** MCP server - **Trust:** 60/100 (B), scored on the content rubric - **Verification:** community-indexed — nobody has claimed this listing - **Version:** 1.0.0 - **Author:** london.taskman - **License:** Unknown - **Endpoints:** streamable-http https://taskman.london/mcp - **Source:** https://taskman.london/mcp - **Endpoint health:** reachable (last checked 2026-10-01T02:06:49.788Z, 6 samples) — uptime is not a security property and is not part of the trust score - **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport) ## Trust 60/100 (B), scored on the content rubric - Publisher verified: no - Install scripts: nothing suspicious found - Prompt-injection scan: clean - Obfuscation scan: clean - Evidence age: 33 days ## Security scan - **Status:** clean - **Scanned:** 2026-09-03T21:20:37.725Z - **Version scanned:** live - **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it. ## Tools 20 declared. Observed from a live `tools/list` probe. - `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. ## Install **Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it. **Cautions** (coverage gaps and advisories — never blocking) - No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it. - No publisher has proved control of this listing; it is indexed, not vouched for. **Config** (claude-code): ```json "{\n \"mcpServers\": {\n \"home-services\": {\n \"type\": \"http\",\n \"url\": \"https://taskman.london/mcp\"\n }\n }\n}" ``` ## Blast radius Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface. - Floor 9, ceiling 27 (tier: unknown) - `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low. - This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score. ## Machine-readable views of this entry - Signed JSON: https://forgeregistry.com/api/v1/packages/london.taskman%2Fhome-services - Install plan: https://forgeregistry.com/api/v1/packages/london.taskman%2Fhome-services/install-plan - Alternatives: https://forgeregistry.com/api/v1/alternatives/london.taskman%2Fhome-services - HTML page: https://forgeregistry.com/registry/london.taskman%2Fhome-services - MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan` ## About this document Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.