Skip to content

TaskMan of London MCP server

london.taskman/home-servicestaskman.londonstreamable-httpv1.0.0Scanned

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

20 tools: 12 change things and 8 only read.

Tools: 0 delete, 0 irreversible, 12 write, 8 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

12 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the TaskMan of London MCP server can do

The TaskMan of London MCP server is published by taskman.london, a domain the MCP Registry verified. It has 20 tools. It can create or change data (12 tools: check_service_area, check_availability, match_providers, create_booking_request and 8 more), but cannot delete data. 8 tools only read.

1 tool can send data out of your system (create_booking_request).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

20 tools

Changes things 12Claude Code: ask
  • check_availabilityUse when the user asks about dates, timing, or whether a service can likely be booked soon.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Use when the user asks about dates, timing, or whether a service can likely be booked soon.
  • check_service_areaUse when the user provides a London postcode or asks whether TaskMan covers their area.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Use when the user provides a London postcode or asks whether TaskMan covers their area.
  • create_booking_requestUse when the user is ready to submit details for a real TaskMan of London booking request.Can send data outNo findings

    Why it is in this group

    • The name "create_booking_request" says "create": a word for a change.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    Use when the user is ready to submit details for a real TaskMan of London booking request.
  • create_customer_bookingUse after verification, detail collection, and confirmed paid payment session to create a booking scoped to the verified customer.No findings

    Why it is in this group

    • The name "create_customer_booking" says "create": a word for a change.
    Description, as the server wrote it
    Use after verification, detail collection, and confirmed paid payment session to create a booking scoped to the verified customer.
  • match_providersUse when an agent needs a single deterministic provider-matching result for assignment.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_paymentUse after collecting booking details to create a Stripe checkout payment session before final booking submission.No findings

    Why it is in this group

    • The name "start_booking_payment" says "start": a word for a change.
    Description, as the server wrote it
    Use after collecting booking details to create a Stripe checkout payment session before final booking submission.
  • start_customer_verificationUse when an existing customer wants to verify identity (OTP or magic link) before assistant-led booking.No findings

    Why it is in this group

    • The name "start_customer_verification" says "start": a word for a change.
    Description, as the server wrote it
    Use when an existing customer wants to verify identity (OTP or magic link) before assistant-led booking.
  • start_trusted_phone_sessionUse 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.No findings

    Why it is in this group

    • The name "start_trusted_phone_session" says "start": a word for a change.
    Description, as the server wrote it
    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_contactUse to add CRM tags to the verified customer for booking workflow tracking.No findings

    Why it is in this group

    • The description's first verb is "add": a word for a change.
    Description, as the server wrote it
    Use to add CRM tags to the verified customer for booking workflow tracking.
  • update_contact_noteUse to append an internal CRM note for the verified customer during or after booking.No findings

    Why it is in this group

    • The name "update_contact_note" says "update": a word for a change.
    Description, as the server wrote it
    Use to append an internal CRM note for the verified customer during or after booking.
  • verify_customer_otpUse after sending an OTP challenge, to verify the one-time passcode and open a short-lived booking session.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Use after sending an OTP challenge, to verify the one-time passcode and open a short-lived booking session.
Only reads 8Show 8 read-only tools
  • find_servicesUse when the user needs help identifying which TaskMan of London service fits their job, especially for vague home-service requests in London.No findings

    Why it is in this group

    • The name "find_services" says "find": a word for reading.
    Description, as the server wrote it
    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_statusUse to check whether a booking payment session is pending, paid, failed, canceled, or expired before attempting booking creation.No findings

    Why it is in this group

    • The name "get_booking_payment_status" says "get": a word for reading.
    Description, as the server wrote it
    Use to check whether a booking payment session is pending, paid, failed, canceled, or expired before attempting booking creation.
  • get_booking_statusUse when the user already has a TaskMan booking request and wants an update.No findings

    Why it is in this group

    • The name "get_booking_status" says "get": a word for reading.
    Description, as the server wrote it
    Use when the user already has a TaskMan booking request and wants an update.
  • get_customer_availabilityUse after verification to check availability for a verified customer at a selected saved address.No findings

    Why it is in this group

    • The name "get_customer_availability" says "get": a word for reading.
    Description, as the server wrote it
    Use after verification to check availability for a verified customer at a selected saved address.
  • get_customer_profileUse after verification to load scoped customer profile details from CRM for booking.No findings

    Why it is in this group

    • The name "get_customer_profile" says "get": a word for reading.
    Description, as the server wrote it
    Use after verification to load scoped customer profile details from CRM for booking.
  • get_quote_estimateUse when the user asks about likely cost, ballpark pricing, or whether a task needs a custom quote.No findings

    Why it is in this group

    • The name "get_quote_estimate" says "get": a word for reading.
    Description, as the server wrote it
    Use when the user asks about likely cost, ballpark pricing, or whether a task needs a custom quote.
  • list_customer_addressesUse after verification to list saved addresses linked to the verified customer.No findings

    Why it is in this group

    • The name "list_customer_addresses" says "list": a word for reading.
    Description, as the server wrote it
    Use after verification to list saved addresses linked to the verified customer.
  • list_service_typesUse after verification to show supported service types before collecting booking details.No findings

    Why it is in this group

    • The name "list_service_types" says "list": a word for reading.
    Description, as the server wrote it
    Use after verification to show supported service types before collecting booking details.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:15 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
12
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 12 tools that change things (12 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://taskman.london/mcp: tools/list returned 20 tools to an anonymous client, including check_service_area (write), check_availability (write), match_providers (write), create_booking_request (write), start_trusted_phone_session (write) and 7 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http home-services https://taskman.london/mcp
claude mcp add --transport http home-services https://taskman.london/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__home-services__find_services",
      "mcp__home-services__get_quote_estimate",
      "mcp__home-services__get_booking_status",
      "mcp__home-services__get_customer_profile",
      "mcp__home-services__list_customer_addresses",
      "mcp__home-services__list_service_types",
      "mcp__home-services__get_customer_availability",
      "mcp__home-services__get_booking_payment_status"
    ],
    "ask": [
      "mcp__home-services__check_service_area",
      "mcp__home-services__check_availability",
      "mcp__home-services__match_providers",
      "mcp__home-services__create_booking_request",
      "mcp__home-services__start_trusted_phone_session",
      "mcp__home-services__start_customer_verification",
      "mcp__home-services__verify_customer_otp",
      "mcp__home-services__verify_magic_link_token",
      "mcp__home-services__start_booking_payment",
      "mcp__home-services__create_customer_booking",
      "mcp__home-services__update_contact_note",
      "mcp__home-services__tag_contact"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as home-services. Review it before you use it.

Capability tags behind 1 rule
  • mcp__home-services__create_booking_request outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/london.taskman/home-services/verify?hash=9a77dd067dd97453cd5aee0231db7b6bd527e0834c5b6dbc751bfd0c536d86a9" | jq -e '.changed == false'

Pinned hash 9a77dd067dd9, from Nov 18, 2026, 18:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/london.taskman/home-services/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for london.taskman/home-services
[![Anlyon Radar](https://radar.anlyon.com/badge/london.taskman/home-services.svg)](https://radar.anlyon.com/servers/london.taskman/home-services)

Source: MCP Registry. Synced Oct 21, 2026, 18:53 UTC.

TaskMan of London MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the TaskMan of London MCP server safe?

No scan can promise that. What its definitions show: 20 tools, 12 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the TaskMan of London MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the TaskMan of London MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the TaskMan of London MCP server have?

20 tools: 12 write, 8 read. check_service_area, check_availability, match_providers, create_booking_request, start_trusted_phone_session, start_customer_verification, verify_customer_otp, verify_magic_link_token and 12 more.

Does the TaskMan of London MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the TaskMan of London MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_booking_request.

Has the TaskMan of London MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.