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

com.handlediq/find-help

https://app.handlediq.com

Registry code: 3b1afd224d7cccb0

api record

HandledIQ runs home service shops (heating and cooling, plumbing, electrical, roofing, pest control, junk removal, demolition and more). For a person's own AI assistant: find_help with what they need and their ZIP finds the shops near them that do it, each with its own book price, all in, its soonest real open time and its signed record (work finished, callbacks, arrivals kept, ratings). hold_time holds one shop's time for 10 minutes and that shop texts the person a link; the visit is booked only when the person taps yes on their own phone, never on your word. booking_status says whether they…

endpoint
https://app.handlediq.com/agents/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 com.handlediq/find-help live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is com.handlediq/find-help free to use?
Yes — the hub reached it with no key and no payment.
What tools does com.handlediq/find-help have?
6 tools: request_service, hold_time, booking_status, get_quote, verify_record, find_help.
Is com.handlediq/find-help 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 100%· all time 100%

latency
581ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 6 tools
6 never probed 0 of 6 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.

  • request_service unknown 1h ago

    Opens HandledIQ's quote window on one shop, for the person themselves: they pick what they need, see the shop's own book price and real open times, and hold a time; the shop texts them and only their tap books it. Returns who the shop is and the work it prices.

    mcp-tool

    {
      "type": "object",
      "required": [
        "business_id"
      ],
      "properties": {
        "business_id": {
          "type": "string",
          "description": "The shop's business_id: its provider_business_id in HandledIQ's business feed, or a find_help answer's."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • hold_time unknown never probed

    Holds one open time from a quote for 10 minutes and has the shop text the person a link to book it or say it was not them. Nothing is booked until the person taps yes. The same call again, while it is held, texts no one. The quote_id may come from any shop find_help or get_quote gave.

    mcp-tool

    {
      "type": "object",
      "required": [
        "quote_id",
        "option_id",
        "time_id",
        "name",
        "mobile",
        "street"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "The person's name."
        },
        "unit": {
          "type": "string",
          "description": "Optional. The unit or apartment."
        },
        "mobile": {
          "type": "string",
          "description": "The person's US mobile number, with its area code. The shop texts it once."
        },
        "street": {
          "type": "string",
          "description": "The street address of the house, with its number."
        },
        "time_id": {
          "type": "string",
          "description": "One of the quote's times, by its time_id."
        },
        "quote_id": {
          "type": "string",
          "description": "The quote_id price gave."
        },
        "option_id": {
          "type": "string",
          "description": "One of the quote's prices, by its option_id."
        }
      },
      "additionalProperties": false
    }
    arguments 42 lines
  • booking_status unknown never probed

    Where a quote stands: priced, waiting on the person (with minutes left on the hold), booked (when and with whom), said it was not them, or the hold ran out. Once booked, what happened after: the tech on the way, arrived (and whether inside the time promised), the visit finished, or canceled by the shop.

    mcp-tool

    {
      "type": "object",
      "required": [
        "quote_id"
      ],
      "properties": {
        "quote_id": {
          "type": "string",
          "description": "The quote_id price gave."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • get_quote unknown never probed

    The shop's own book prices for what the person needs and its next real open times. Returns a quote_id to hold a time with. visit: no fixed price for exactly that, so the price is the shop's visit to find the problem. A price over the shop's limit waits for the owner; work that is not the shop's trade gets no quote. The shop is the one business_id names; kind is one of the kinds request_service gave, or leave it out and say the need in words.

    mcp-tool

    {
      "type": "object",
      "required": [
        "business_id",
        "need",
        "assistant"
      ],
      "properties": {
        "day": {
          "type": "string",
          "description": "Optional. The first day that works for the person, YYYY-MM-DD; times start that day."
        },
        "kind": {
          "type": "string",
          "description": "Optional. One of the shop's kinds of work, as request_service gave them (work[].kind)."
        },
        "need": {
          "type": "string",
          "description": "What the person needs, in a line, like: AC check, a roof leak, ants in the kitchen, or a couch to haul away."
        },
        "assistant": {
          "type": "string",
          "description": "Your own name, as the person you act for knows you, like Muse. It goes in the text the shop sends them."
        },
        "business_id": {
          "type": "string",
          "description": "The shop's business_id: its provider_business_id in HandledIQ's business feed, or a find_help answer's."
        },
        "budget_dollars": {
          "type": "number",
          "description": "Optional. The most the person wants to pay, in dollars."
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
  • verify_record unknown 1h ago

    Checks a signed record from any HandledIQ shop (a house's, a technician's or a shop's): valid, with who signed it and the record it holds, or not valid and why. Anyone can make the same check with the key at the issuer's id.

    mcp-tool

    {
      "type": "object",
      "required": [
        "signed"
      ],
      "properties": {
        "signed": {
          "type": "string",
          "description": "The signed form a record came with (signed, or signed_record): a compact JWS, up to a million characters."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • find_help unknown never probed

    The shops on HandledIQ near a US ZIP code that can do what the person needs: each with its book prices, its soonest open times, its signed record and a quote_id to hold a time with. Soonest first, three at most.

    mcp-tool

    {
      "type": "object",
      "required": [
        "need",
        "zip",
        "assistant"
      ],
      "properties": {
        "day": {
          "type": "string",
          "description": "Optional. The first day that works for the person, YYYY-MM-DD."
        },
        "zip": {
          "type": "string",
          "description": "The house's 5-digit US ZIP code."
        },
        "need": {
          "type": "string",
          "description": "What the person needs, in a line, like: AC not cooling, a roof leak, ants in the kitchen, or a couch to haul away."
        },
        "assistant": {
          "type": "string",
          "description": "Your own name, as the person you act for knows you, like Muse. It goes in the text the shop sends them."
        },
        "budget_dollars": {
          "type": "number",
          "description": "Optional. The most the person wants to pay, in dollars."
        }
      },
      "additionalProperties": false
    }
    arguments 31 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 3b1afd224d7cccb0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3b1afd224d7cccb0/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/3b1afd224d7cccb0/badge.svg)](https://brick.blue/agent/3b1afd224d7cccb0?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
100%

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.