# LossHQ Directory (remote · www.losshq.com)

Search certified insurance appraisers and umpires by state, city, role and specialty.

- Trust score: 63/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `www.losshq.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-losshq-directory/www.md), [page](https://verifymcp.io/servers/com-losshq-directory/www)

## Channel facts

- Endpoint: `https://www.losshq.com/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-11-04.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the LossHQ Directory MCP server?

LossHQ Directory is a hosted endpoint at https://www.losshq.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-losshq-directory 'https://www.losshq.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-losshq-directory": {
      "url": "https://www.losshq.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-losshq-directory": {
      "type": "http",
      "url": "https://www.losshq.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-losshq-directory]
url = "https://www.losshq.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-losshq-directory": {
      "type": "remote",
      "url": "https://www.losshq.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-losshq-directory --url 'https://www.losshq.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-losshq-directory:
    url: "https://www.losshq.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-losshq-directory": {
      "Transport": "http",
      "Url": "https://www.losshq.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-losshq-directory -t streamable-http -u 'https://www.losshq.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-losshq-directory": {
      "type": "http",
      "url": "https://www.losshq.com/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-11-04 (score 63, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Stability: 0.33 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-02 (score 63, +1)

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

### 2026-10-31 (score 62, +1)

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

### 2026-10-29 (score 61, +1)

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

### 2026-10-26 (score 60, +1)

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

### 2026-10-25 (score 59, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-24 (score 59)

First indexed and scored.

## MCP tools (3)

### `search_appraisers` (~74 tokens)

Search Appraisers

Search LossHQ's directory of certified insurance appraisers and umpires by location, role, specialty, or certification.

Input parameters:

- `certification` (string)
- `city` (string)
- `query` (string)
- `role` (string)
- `specialty` (string)
- `state` (string)

### `get_appraiser_profile` (~29 tokens)

Get Appraiser Profile

Get one LossHQ professional's full public profile by username.

Input parameters:

- `username` (string, required)

### `explain_appraisal_process` (~19 tokens)

Explain Appraisal Process

Explain the insurance appraisal process (neutral overview).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-losshq-directory/www#diagnostics

## Score history

- 2026-11-04: 63
- 2026-11-03: 63
- 2026-11-02: 63
- 2026-11-01: 62
- 2026-10-31: 62
- 2026-10-30: 61
- 2026-10-29: 61
- 2026-10-28: 60
- 2026-10-27: 60
- 2026-10-26: 60
- 2026-10-25: 59
- 2026-10-24: 59

## Common questions

### What is the LossHQ Directory MCP server?

LossHQ Directory is an MCP server listed in the public MCP registry as com.losshq/directory. Search certified insurance appraisers and umpires by state, city, role and specialty. This page covers its hosted endpoint (https://www.losshq.com/mcp).

### Is the LossHQ Directory MCP server safe to use?

LossHQ Directory scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the LossHQ Directory MCP server expose?

LossHQ Directory exposes 3 tools: search_appraisers, get_appraiser_profile, explain_appraisal_process. Their descriptions and schemas cost roughly 122 tokens of context every time the server is loaded.

### Does the LossHQ Directory MCP server require authentication?

Its publisher declares no required credentials for LossHQ Directory. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the LossHQ Directory MCP server still maintained?

LossHQ Directory is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.losshq.com/mcp
- Website: https://www.losshq.com/for-agents
- Changelog RSS feed: https://verifymcp.io/servers/com-losshq-directory/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-losshq-directory/www.json
- HTML version of this page: https://verifymcp.io/servers/com-losshq-directory/www