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

Philadelphia Restoration

https://mcp.philadelphiarestoration.org

Registry code: 217e837cb512020e

api record

Philadelphia water and fire damage restoration: assessment, insurance, costs, and knowledge search.

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

endpoint
https://mcp.philadelphiarestoration.org/mcp/v1
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 Philadelphia Restoration live?
No — it has stopped answering the hub's checks (checked 1h ago). It answered 98% of checks over the last 30 days.
Is Philadelphia Restoration free to use?
Not measured yet.
What tools does Philadelphia Restoration have?
7 tools: search_restoration_knowledge, estimate_cost, assess_damage, check_insurance_coverage, get_emergency_steps, get_local_info, request_callback.
Is Philadelphia Restoration 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
down
uptime, 30 days
97.8%

90 days 98.3%· all time 98.3%

latency
305ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 358 checks · signed record
  • degraded → down· HTTP 503
  • live → degraded· HTTP 503
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • assess water or fire damage
  • check insurance coverage for home damage
  • estimate restoration costs
  • get emergency steps for water damage
  • request a restoration callback
takes → gives
text → data, text
tools
6 reads1 sends messages
_ 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 7 tools
7 never probed 0 of 7 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.

  • search_restoration_knowledge reads unknown never probed

    Semantic search across 60+ expert documents covering water and fire damage restoration. Topics include drying science, moisture mapping, equipment protocols, mold prevention (IICRC S520), fire restoration (IICRC S700), insurance adjuster tactics, contractor evaluation, and Philadelphia housing patterns. Returns relevant excerpts with source citations and relevance scores. Grounded in IICRC standards with section numbers.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Natural language search query (max 1000 characters)"
        }
      }
    }
    arguments 12 lines
  • estimate_cost reads unknown never probed

    Returns Philadelphia-area restoration cost estimates broken down by service type. Includes per-unit pricing (per sq ft, per hour), labor rates ($64-$183/hr), factors that increase or decrease total cost (pre-1978 homes, rowhouse access, code upgrades), and insurance deductible guidance. Based on current Philadelphia metro market data.

    mcp-tool

    {
      "type": "object",
      "required": [
        "damage_type",
        "severity"
      ],
      "properties": {
        "severity": {
          "enum": [
            "minor",
            "moderate",
            "severe",
            "catastrophic"
          ],
          "type": "string",
          "description": "Assessed severity level"
        },
        "damage_type": {
          "type": "string",
          "description": "Type of damage for cost estimation"
        }
      }
    }
    arguments 23 lines
  • assess_damage reads unknown never probed

    Returns structured damage assessment for water and fire damage in Philadelphia residential properties. Classifies 13 damage types by severity, provides prioritized immediate safety actions, estimates restoration costs with Philadelphia market rates, and includes neighborhood-specific risk context. Based on IICRC S500/S520/S700 standards and field experience from Philadelphia restoration companies.

    mcp-tool

    {
      "type": "object",
      "required": [
        "damage_type"
      ],
      "properties": {
        "damage_type": {
          "enum": [
            "burst_pipe",
            "flooding",
            "sewage_backup",
            "appliance_leak",
            "roof_leak",
            "bathroom_overflow",
            "sprinkler_malfunction",
            "ice_dam",
            "structural_fire",
            "kitchen_fire",
            "electrical_fire",
            "smoke_damage",
            "arson"
          ],
          "type": "string",
          "description": "Type of water or fire damage to assess"
        },
        "neighborhood": {
          "type": "string",
          "description": "Philadelphia neighborhood (e.g., 'fishtown', 'center-city')"
        }
      }
    }
    arguments 31 lines
  • check_insurance_coverage reads unknown never probed

    Returns Pennsylvania insurance coverage analysis for water and fire damage claims. Evaluates coverage likelihood by HO policy type (HO-1 through HO-6), applies PA-specific regulations including bad faith statute (42 Pa.C.S. § 8371) and Act 119, and provides step-by-step claims process guidance with common denial reasons and appeals strategies.

    mcp-tool

    {
      "type": "object",
      "required": [
        "damage_type"
      ],
      "properties": {
        "cause": {
          "type": "string",
          "description": "Specific cause of damage (e.g., 'frozen pipes', 'grease fire')"
        },
        "damage_type": {
          "type": "string",
          "description": "Type of water or fire damage"
        },
        "policy_type": {
          "enum": [
            "HO-1",
            "HO-2",
            "HO-3",
            "HO-4",
            "HO-5",
            "HO-6"
          ],
          "type": "string",
          "description": "Homeowner's insurance policy type (default: HO-3)"
        }
      }
    }
    arguments 28 lines
  • get_emergency_steps reads unknown never probed

    Returns prioritized, time-critical emergency action steps for active water or fire damage in Philadelphia. Includes safety warnings, step-by-step instructions with time sensitivity flags, Philadelphia emergency contacts (PWD, PECO, PGW, Philadelphia Fire Department), and documentation checklist for insurance claims. Use this tool FIRST when a homeowner has an active emergency.

    mcp-tool

    {
      "type": "object",
      "required": [
        "damage_type"
      ],
      "properties": {
        "damage_type": {
          "type": "string",
          "description": "Type of active emergency damage"
        }
      }
    }
    arguments 12 lines
  • get_local_info reads unknown never probed

    Returns Philadelphia-specific local information for damage restoration. Covers 6+ neighborhoods with housing stock analysis (rowhouses, twins, pre-war construction), common damage patterns, flood risk levels, emergency utility contacts, building code requirements, and seasonal risk factors. Helps agents provide neighborhood-aware guidance to Philadelphia homeowners.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "info_type": {
          "enum": [
            "neighborhood",
            "city"
          ],
          "type": "string",
          "description": "Type of info: neighborhood-specific or city-wide (default: city)"
        },
        "neighborhood": {
          "type": "string",
          "description": "Philadelphia neighborhood slug (e.g., 'fishtown', 'south-philly')"
        }
      }
    }
    arguments 18 lines
  • request_callback sends messages unknown never probed

    Submits a callback request for a Philadelphia homeowner dealing with water or fire damage. A restoration concierge calls back within 15 minutes during business hours (Mon-Fri 8am-6pm ET) to assess the situation and connect with vetted local professionals. Requires phone number and situation description. Returns a reference number for tracking.

    mcp-tool

    {
      "type": "object",
      "required": [
        "phone"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Homeowner's name (optional)"
        },
        "phone": {
          "type": "string",
          "description": "Phone number for callback (US format)"
        },
        "situation": {
          "type": "string",
          "description": "Brief description of the damage situation"
        }
      }
    }
    arguments 20 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 217e837cb512020e.

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