_ registry / mcp streamable-http · checked 1h ago

taskrabbit-booking-assistant

https://mcp.taskrabbit.com

Registry code: fe217eb86d1fa8cf

api record

The Taskrabbit MCP connector lets Claude check service availability and pricing in the user's location. When a service is available, Claude guides the user through scoping questions to understand their needs — such as room count, space type, and other relevant details — then surfaces accurate local pricing and connects them with a booking link.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.taskrabbit.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is taskrabbit-booking-assistant live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is taskrabbit-booking-assistant free to use?
Yes — the hub reached it with no key and no payment.
What tools does taskrabbit-booking-assistant have?
3 tools: list_supported_services, check_service_availability, generate_deep_link.
Is taskrabbit-booking-assistant safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.3%· all time 99.3%

latency
558ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 303 checks · signed record
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • check service availability
  • list supported services
  • generate booking link
takes → gives
data → data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_supported_services reads unknown 19h ago

    List Taskrabbit services available in a location. Provide either city + state OR postalCode.

    mcp-tool

    {
      "type": "object",
      "anyOf": [
        {
          "required": [
            "city",
            "state"
          ]
        },
        {
          "required": [
            "postalCode"
          ]
        }
      ],
      "properties": {
        "city": {
          "type": "string",
          "description": "City name (e.g., New York, San Francisco)"
        },
        "state": {
          "type": "string",
          "description": "State/province abbreviation (e.g., NY, CA)"
        },
        "postalCode": {
          "type": "string",
          "pattern": "^\\d{5}$",
          "description": "US postal code (e.g., 10001)"
        }
      }
    }
    arguments 31 lines
  • check_service_availability reads unknown 19h ago

    Check availability, pricing, and scoping questions for a service in a location. Provide either city + state OR postalCode to specify the location. When the response includes topTaskers, render each tasker as a visual card (not a plain list or table) with a circular avatar showing their initials, name, rating, review count, and description.

    mcp-tool

    {
      "type": "object",
      "anyOf": [
        {
          "required": [
            "city",
            "state"
          ]
        },
        {
          "required": [
            "postalCode"
          ]
        }
      ],
      "required": [
        "service"
      ],
      "properties": {
        "city": {
          "type": "string",
          "description": "City name (e.g., New York, San Francisco)"
        },
        "state": {
          "type": "string",
          "description": "State/province abbreviation (e.g., NY, CA)"
        },
        "service": {
          "type": "string",
          "description": "The service the user asked for, in their own words (e.g., 'assemble IKEA furniture')"
        },
        "postalCode": {
          "type": "string",
          "pattern": "^\\d{5}$",
          "description": "US postal code (e.g., 10001)"
        }
      }
    }
    arguments 38 lines
  • generate_deep_link reads unknown 27d ago

    Generate a pre-filled Taskrabbit booking deep link using task template ID.

    mcp-tool

    {
      "type": "object",
      "required": [
        "categoryId",
        "locale",
        "questionnaire"
      ],
      "properties": {
        "locale": {
          "enum": [
            "en-US"
          ],
          "type": "string",
          "description": "BCP 47 locale code (e.g., 'en-US')"
        },
        "categoryId": {
          "type": "string",
          "description": "Category service key (e.g., 'furniture_assembly')"
        },
        "questionnaire": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "question",
              "answer"
            ],
            "properties": {
              "param": {
                "type": "string",
                "description": "URL parameter key from the scoping question (e.g., 'cleaning_type'). Use the param value from the scopingQuestions returned by check_service_availability."
              },
              "answer": {
                "type": "string",
                "description": "The answer to the question"
              },
              "question": {
                "type": "string",
                "description": "The question that was asked"
              }
            }
          },
          "description": "Ordered list of question/answer pairs from the scoping conversation"
        }
      }
    }
    arguments 46 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id fe217eb86d1fa8cf.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/fe217eb86d1fa8cf/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/fe217eb86d1fa8cf/badge.svg)](https://brick.blue/agent/fe217eb86d1fa8cf?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.