FindingLeads
REMOTE · FINDINGLEADS.COM
Missed-call cost by trade, setup pricing, Google local presence and Pro Sites for contractors.
Available components
Last scanned (14 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Marketing and SEO
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 736 tokens (~73/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://findingleads.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=findingleads.com | CN=YR1,O=Let's Encrypt,C=US | 19 Oct 2026 | 17 Jan 2027 | RSA 2048 | SHA256-RSA | 525b9ee58b3def417d618b96d913b65b955 |
| SANs: findingleads.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of findingleads.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| findingleads.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://findingleads.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://findingleads.com/api/mcp | HTTPS enforced | 308 | https://findingleads.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
estimate_missed_call_cost ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| calls_per_month | number | – | Inbound calls the business receives in a month |
| trade | string | yes | e.g. hvac, plumbing, roofing, electrical, restoration |
No output schema declared.
No examples provided.
get_offer ~49
What FindingLeads does for a home-service business (HVAC, plumbing, roofing, electrical, restoration), who it is for, and the next step. Read this before describing the service to anyone.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_pricing ~61
How FindingLeads is priced: the free trial, how monthly plans work, and every one-time done-for-you setup (Google Business Profile, Local Services Ads, reviews, Pro Site, speed-to-lead and more) with its public price and page.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_pro_site ~55
What a FindingLeads Pro Site is (a contractor website built to turn a visitor into a booked call), the pages it has, what the owner edits versus what stays fixed, what it costs, and where to start one.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
google_business_profile_checklist ~72
The steps to get a local service business found on Google: Business Profile claim, verification and build-out, Local Services Ads and the Google Guaranteed badge, consistent directory listings, and a review system. Usable as a do-it-yourself checklist; each part also names the done-for-you setup and its price.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
how_to_fix ~73
For one common reason a contractor loses jobs (missed calls, slow follow-up, few reviews, not showing up on Google or AI search, no website): why it costs jobs and what FindingLeads does about it, with the page to start on.
| Name | Type | Req | Description |
|---|---|---|---|
| problem | string | yes | Which problem the business has. |
No output schema declared.
No examples provided.
list_free_checks ~75
The free checks a contractor can run on findingleads.com: the 60-second website audit, the missing-leads count for their trade and area, and the Google opportunity scan. Returns what each one answers and the link to run it. Each check is run by the user on the site, which emails them the report.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_trades ~49
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pro_site_custom_domain ~42
How a contractor puts their Pro Site on a domain they own, what changes for search when they do, and what happens if they keep the directory address instead.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pro_site_start_link ~105
The link that starts a FindingLeads Pro Site draft, with the business name, trade and city filled in when given. The user enters their own email on the page; never ask for it in the chat.
| Name | Type | Req | Description |
|---|---|---|---|
| business_name | string | – | The business name, if the user gave it. |
| city | string | – | Primary city, e.g. Phoenix, AZ |
| trade | string | – | e.g. HVAC, Plumbing, Roofing, Electrical, Restoration |
No output schema declared.
No examples provided.
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.
remote · findingleads.com
claude mcp add --transport http com-findingleads-findingleads 'https://findingleads.com/api/mcp'
What is the FindingLeads MCP server?
FindingLeads is an MCP server listed in the public MCP registry as com.findingleads/findingleads. Missed-call cost by trade, setup pricing, Google local presence and Pro Sites for contractors. This page covers its hosted endpoint (https://findingleads.com/api/mcp).
Is the FindingLeads MCP server safe to use?
FindingLeads scores 87 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 10 tools: get_offer, get_pricing, estimate_missed_call_cost, list_trades, how_to_fix, and 5 more. Their descriptions and schemas cost roughly 682 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the FindingLeads MCP server?
VerifyMCP ran 13 checks on FindingLeads, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.