# TaskMan of London

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

- name: london.taskman/home-services
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 71/100 flags: no-repository
- quality: 79/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/london.taskman%2Fhome-services
- tools: https://api.protogrid.dev/v1/servers/london.taskman%2Fhome-services/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "home-services": {
      "type": "http",
      "url": "https://taskman.london/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 98
- freshness: 45
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-96% -stale-203d -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 79/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 71 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: get_booking_status (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); update_contact_note (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); find_services (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 2,830 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 20, about 2,830 tokens to load them all
- tool set hash: 0100adf0f60dd91c6ba2f822e33216f7
- badge: [![protogrid quality](https://protogrid.dev/badge/london.taskman/home-services.svg)](https://protogrid.dev/servers/london.taskman/home-services)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://taskman.london/mcp (streamable-http, auth none, reachable true, uptime30d 0.95614034)

## Packages

_none_

## Tools (20)

- `check_availability`: Use when the user asks about dates, timing, or whether a service can likely be booked soon.
- `check_service_area`: Use when the user provides a London postcode or asks whether TaskMan covers their area.
- `create_booking_request`: Use when the user is ready to submit details for a real TaskMan of London booking request.
- `create_customer_booking`: Use after verification, detail collection, and confirmed paid payment session to create a booking scoped to the verified customer.
- `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.
- `get_booking_payment_status`: Use to check whether a booking payment session is pending, paid, failed, canceled, or expired before attempting booking creation.
- `get_booking_status`: Use when the user already has a TaskMan booking request and wants an update.
- `get_customer_availability`: Use after verification to check availability for a verified customer at a selected saved address.
- `get_customer_profile`: Use after verification to load scoped customer profile details from CRM for booking.
- `get_quote_estimate`: Use when the user asks about likely cost, ballpark pricing, or whether a task needs a custom quote.
- `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.
- `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.
- `start_booking_payment`: Use after collecting booking details to create a Stripe checkout payment session before final booking submission.
- `start_customer_verification`: Use when an existing customer wants to verify identity (OTP or magic link) before assistant-led booking.
- `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.
- `tag_contact`: Use to add CRM tags to the verified customer for booking workflow tracking.
- `update_contact_note`: Use to append an internal CRM note for the verified customer during or after 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.