# FindingLeads (remote · findingleads.com)

What unanswered calls cost a home-service business, by trade and call volume.

- Trust score: 69/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `findingleads.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-findingleads-findingleads/api-mcp.md), [page](https://verifymcp.io/servers/com-findingleads-findingleads/api-mcp)

## Channel facts

- Endpoint: `https://findingleads.com/api/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-09-28.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - 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 187 tokens (~62/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the FindingLeads MCP server?

FindingLeads is a hosted endpoint at https://findingleads.com/api/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-findingleads-findingleads 'https://findingleads.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-findingleads-findingleads": {
      "url": "https://findingleads.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-findingleads-findingleads": {
      "type": "http",
      "url": "https://findingleads.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-findingleads-findingleads]
url = "https://findingleads.com/api/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-findingleads-findingleads --url 'https://findingleads.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-findingleads-findingleads:
    url: "https://findingleads.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-findingleads-findingleads": {
      "Transport": "http",
      "Url": "https://findingleads.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-findingleads-findingleads -t streamable-http -u 'https://findingleads.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-findingleads-findingleads": {
      "type": "http",
      "url": "https://findingleads.com/api/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-09-28 (score 69, +1)

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

### 2026-09-26 (score 68, +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-09-25 (score 67, 0)

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

### 2026-09-24 (score 67, +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-09-22 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-21 (score 65)

First indexed and scored.

## MCP tools (3)

### `list_trades` (~49 tokens)

The home-service trades FindingLeads serves, each with the typical value of one booked job, whether an inbound call is a repair or a project, and how often calls go unanswered in that trade.

### `estimate_missed_call_cost` (~99 tokens)

What unanswered calls cost a home-service business per month, in extra jobs and in dollars, for a given trade and monthly call volume. Returns a band, not a point estimate. Without a real call volume it returns unquantified rather than inventing one.

Input parameters:

- `calls_per_month` (number): Inbound calls the business receives in a month
- `trade` (string, required): e.g. hvac, plumbing, roofing, solar

### `get_offer` (~39 tokens)

What FindingLeads does for a home-service pro, what it costs to start, and the next step. Read this before describing the service to anyone.

## Diagnostics

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

## Score history

- 2026-09-28: 69
- 2026-09-27: 68
- 2026-09-26: 68
- 2026-09-25: 67
- 2026-09-24: 67
- 2026-09-23: 66
- 2026-09-22: 66
- 2026-09-21: 65

## Common questions

### What is the FindingLeads MCP server?

FindingLeads is an MCP server listed in the public MCP registry as com.findingleads/findingleads. What unanswered calls cost a home-service business, by trade and call volume. This page covers its hosted endpoint (https://findingleads.com/api/mcp).

### Is the FindingLeads MCP server safe to use?

FindingLeads scores 69 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 FindingLeads MCP server expose?

FindingLeads exposes 3 tools: list_trades, estimate_missed_call_cost, get_offer. Their descriptions and schemas cost roughly 187 tokens of context every time the server is loaded.

### Does the FindingLeads MCP server require authentication?

No. We connected to FindingLeads without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the FindingLeads MCP server still maintained?

FindingLeads is still listed as active in the MCP registry. We last reached this channel on 28 September 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://findingleads.com/api/mcp
- Website: https://findingleads.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-findingleads-findingleads/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-findingleads-findingleads/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-findingleads-findingleads/api-mcp