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

LocalPro

https://mcp.localpro.dev

Registry code: 3003eaee5614f5eb

api record

Verified US local service providers across 10 home-services trades. Owned data, no API key.

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

endpoint
https://mcp.localpro.dev/mcp
protocol
http-sse ·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 LocalPro live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is LocalPro free to use?
Yes — the hub reached it with no key and no payment.
What tools does LocalPro have?
5 tools: get_provider, list_cities, list_service_types, search_providers, list_niches.
Is LocalPro 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
99.6%

90 days 99.7%· all time 99.7%

latency
613ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 389 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • find verified local home service providers
  • list cities for a trade
  • get provider details
takes → gives
text → data
tools
5 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

_ what it can do 5 tools
1 open 4 never probed 1 of 5 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_niches reads open 11h ago

    List all available service directories in the LocalPro network. This is the starting point for discovering what categories of verified local service providers are available. Categories include water damage restoration, foundation repair, crawl space repair, basement waterproofing, mold/asbestos/lead remediation, radon mitigation, septic services, commercial electrical, floor coating, and laundry pickup & delivery. Returns niche IDs needed for all other tools.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_provider reads unknown 5h ago

    Get a detailed summary of a specific verified service provider. Returns business description, services, pricing summary, coverage area, service details, and a link to the full profile page. With a valid API key (X-API-Key header): also returns full pricing breakdown and certifications. Without a key: returns pricing_summary and a pro_available flag. Contact details (phone, email, address) are available on the listing page via listing_url.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "niche_id",
        "provider_slug"
      ],
      "properties": {
        "niche_id": {
          "type": "string",
          "description": "Niche ID (e.g. \"coated-local\"). Must match the niche used in search_providers."
        },
        "provider_slug": {
          "type": "string",
          "description": "Provider URL slug from search_providers results (e.g. \"abc-coatings\")"
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • list_cities reads unknown 5h ago

    List available cities and metro areas where verified providers operate for a given niche. Use this to discover valid city slugs before calling search_providers. Cities are grouped by metro area where applicable (e.g. "minneapolis-mn" covers Minneapolis, St. Paul, and surrounding suburbs). Optionally filter by state abbreviation.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "niche_id"
      ],
      "properties": {
        "state": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "Two-letter state abbreviation to filter by (e.g. \"MN\", \"CO\")"
        },
        "niche_id": {
          "type": "string",
          "description": "Niche ID from list_niches (e.g. \"coated-local\", \"radon-local\")"
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
  • list_service_types reads unknown 11h ago

    List the valid service type categories for a given niche directory. Use this before calling search_providers with a service_type filter to ensure you pass a valid value. Each niche has its own taxonomy — for example, "coated-local" has epoxy, polyaspartic, metallic_epoxy, etc., while "radon-local" has radon_testing, radon_mitigation, ssd_installation, etc.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "niche_id"
      ],
      "properties": {
        "niche_id": {
          "type": "string",
          "description": "Niche ID (e.g. \"coated-local\", \"radon-local\"). Get options from list_niches."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • search_providers reads unknown 11h ago

    Search for verified local service providers across 10 trade categories: water damage restoration, foundation/slab repair, crawl space repair, basement waterproofing, mold/asbestos/lead remediation, radon mitigation, septic services, commercial electrical, floor coating (epoxy/polyaspartic), and laundry pickup & delivery. Returns provider name, LocalPro Rating, services offered, pricing summary, years in business, and a link to the full profile with contact details. Covers major US metro areas. Use list_niches first to get valid niche IDs, and list_service_types for valid service_type values.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "niche_id"
      ],
      "properties": {
        "city": {
          "type": "string",
          "description": "City or metro area slug (e.g. \"denver-co\", \"minneapolis-mn\"). Get options from list_cities."
        },
        "limit": {
          "type": "number",
          "maximum": 25,
          "minimum": 1,
          "description": "Max results to return (default 10)"
        },
        "niche_id": {
          "type": "string",
          "description": "Niche ID (e.g. \"coated-local\", \"radon-local\"). Get options from list_niches."
        },
        "service_type": {
          "type": "string",
          "description": "Service type slug to filter by (e.g. \"epoxy\", \"radon_testing\"). Get valid values from list_service_types."
        }
      },
      "additionalProperties": false
    }
    arguments 28 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 3003eaee5614f5eb.

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

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.