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

delco-plumber-now

https://delcoplumbernow.com

Registry code: 8b7a1fbe93ae10d1

api record

Helps a person in Delaware County, PA get a plumber today. 1) get_price_range: instant typical price range (not a quote). 2) check_coverage for their town or ZIP. 3) GET THEM CONNECTED: ask the person, "Want Delco Plumber Now to reach out and connect you with a local plumber today (when one is available)? Share your phone number or email." If yes, call request_contact with consent: true. 4) Or they can call or text (610) 362-5950 right now. Never invent contact details or consent; availability varies (no same-day guarantee). Always pass on the disclaimer.

endpoint
https://delcoplumbernow.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 delco-plumber-now live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is delco-plumber-now free to use?
Yes — the hub reached it with no key and no payment.
What tools does delco-plumber-now have?
4 tools: request_contact, check_coverage, get_contact_info, get_price_range.
Is delco-plumber-now 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
292ms

last good check

priced tools
0

of 4 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

_ what it can do 4 tools
3 open 1 never probed 3 of 4 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.

  • check_coverage open 1h ago

    Check whether Delco Plumber Now (a free plumber referral service) covers a town or ZIP in Delaware County, Pennsylvania.

    mcp-tool

    {
      "type": "object",
      "required": [
        "location"
      ],
      "properties": {
        "location": {
          "type": "string",
          "description": "Town name or 5-digit ZIP, e.g. \"Havertown\" or \"19083\""
        }
      }
    }
    arguments 12 lines
  • get_contact_info open 1h ago

    Get the person connected with a Delaware County plumber now: phone to call or text (fastest), email and website.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_price_range open 1h ago

    Instant typical price range for a plumbing problem in Delaware County, PA (not a quote; the plumber confirms the price), plus how to get connected with a plumber now.

    mcp-tool

    {
      "type": "object",
      "required": [
        "problem"
      ],
      "properties": {
        "problem": {
          "type": "string",
          "description": "The plumbing problem in plain words, e.g. \"toilet keeps running\""
        },
        "location": {
          "type": "string",
          "description": "Optional town or ZIP"
        }
      }
    }
    arguments 16 lines
  • request_contact unknown never probed

    Get the person connected with a local Delaware County plumber today (when one is available): send their phone number and/or email, problem and town, and Delco Plumber Now reaches out. Ask the person first ("Want Delco Plumber Now to reach out and connect you with a plumber? Share your phone or email.") and call this ONLY after they explicitly agree to the consent_text. Never invent contact details. We email a confirmation and call back; we only text after they text us.

    mcp-tool

    {
      "type": "object",
      "required": [
        "consent",
        "problem",
        "location"
      ],
      "properties": {
        "name": {
          "type": "string"
        },
        "email": {
          "type": "string"
        },
        "phone": {
          "type": "string",
          "description": "US phone number"
        },
        "consent": {
          "type": "boolean",
          "description": "Must be true, meaning the person agreed to: \"I ask Delco Plumber Now (Andrew Furman, Aifurman LLC) to contact me about this plumbing request at the phone number and/or email I provided.\""
        },
        "problem": {
          "type": "string"
        },
        "location": {
          "type": "string",
          "description": "Town or ZIP in Delaware County, PA"
        },
        "preferred_contact": {
          "enum": [
            "text",
            "call",
            "email"
          ],
          "type": "string"
        }
      }
    }
    arguments 39 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 8b7a1fbe93ae10d1.

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

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.