# Philadelphia Restoration (remote · mcp.philadelphiarestoration.org)

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

- Trust score: 65/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.philadelphiarestoration.org`: 65/100 (this document), [markdown](https://verifymcp.io/servers/lucasnoah-philadelphia-restoration/mcp.md), [page](https://verifymcp.io/servers/lucasnoah-philadelphia-restoration/mcp)

## Channel facts

- Endpoint: `https://mcp.philadelphiarestoration.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 51/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (assess_damage).
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 765 tokens (~109/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http lucasnoah-philadelphia-restoration https://mcp.philadelphiarestoration.org/mcp
```

### Codex

```toml
[mcp_servers.lucasnoah-philadelphia-restoration]
url = "https://mcp.philadelphiarestoration.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lucasnoah-philadelphia-restoration": {
      "type": "remote",
      "url": "https://mcp.philadelphiarestoration.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lucasnoah-philadelphia-restoration --url https://mcp.philadelphiarestoration.org/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  lucasnoah-philadelphia-restoration:
    url: "https://mcp.philadelphiarestoration.org/mcp"
```

### Other

```json
{
  "mcpServers": {
    "lucasnoah-philadelphia-restoration": {
      "type": "http",
      "url": "https://mcp.philadelphiarestoration.org/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 63, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 62)

First indexed and scored.

## MCP tools (7)

### `assess_damage` (~109 tokens)

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.

Input parameters:

- `damage_type` (string, required): Type of water or fire damage to assess
- `neighborhood` (string): Philadelphia neighborhood (e.g., 'fishtown', 'center-city')

### `check_insurance_coverage` (~138 tokens)

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.

Input parameters:

- `cause` (string): Specific cause of damage (e.g., 'frozen pipes', 'grease fire')
- `damage_type` (string, required): Type of water or fire damage
- `policy_type` (string): Homeowner's insurance policy type (default: HO-3)

### `estimate_cost` (~99 tokens)

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.

Input parameters:

- `damage_type` (string, required): Type of damage for cost estimation
- `severity` (string, required): Assessed severity level

### `get_emergency_steps` (~88 tokens)

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.

Input parameters:

- `damage_type` (string, required): Type of active emergency damage

### `get_local_info` (~112 tokens)

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.

Input parameters:

- `info_type` (string): Type of info: neighborhood-specific or city-wide (default: city)
- `neighborhood` (string): Philadelphia neighborhood slug (e.g., 'fishtown', 'south-philly')

### `request_callback` (~113 tokens)

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.

Input parameters:

- `name` (string): Homeowner's name (optional)
- `phone` (string, required): Phone number for callback (US format)
- `situation` (string): Brief description of the damage situation

### `search_restoration_knowledge` (~106 tokens)

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.

Input parameters:

- `query` (string, required): Natural language search query (max 1000 characters)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/lucasnoah-philadelphia-restoration/mcp#diagnostics

## Score history

- 2026-08-03: 65
- 2026-08-02: 64
- 2026-08-01: 64
- 2026-07-31: 63
- 2026-07-30: 65
- 2026-07-29: 64
- 2026-07-28: 63
- 2026-07-27: 63
- 2026-07-26: 62

## Links

- Remote endpoint: https://mcp.philadelphiarestoration.org/mcp
- Changelog RSS feed: https://verifymcp.io/servers/lucasnoah-philadelphia-restoration/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/lucasnoah-philadelphia-restoration/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/lucasnoah-philadelphia-restoration/mcp