com.findingleads/findingleads
FindingLeads
com.findingleads/findingleads costs 243 tokens of context per session. It has 3 tool definitions. That is 0.1 % of a 200k window. Measured 2026-10-03.
What unanswered calls cost a home-service business, by trade and call volume.
alive probed 2026-10-03 · HTTP 200
3tools
243tokens for the tool definitions
0.1 %of a 200k context window
915 msto initialize
967 msto list tools
- Endpoint
- https://findingleads.com/api/mcp (streamable-http)
- Host
- findingleads.com
- Protocol
- 2025-06-18
- Reports itself as
- findingleads 1.0.0
- Capabilities
- tools
- Instructions
- none
- Website
- https://findingleads.com
- Registry
- active, updated 2026-09-21 · registry entry
- Reachable
- 2 of the last 2 probes
Most expensive tools
| Tool | Tokens | Share of this server |
|---|---|---|
| estimate_missed_call_cost | 123 | 51 % |
| list_trades | 65 | 27 % |
| get_offer | 55 | 23 % |
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Tokens |
|---|---|---|---|---|
| 2026-10-03 20:29 | alive | 915 ms | 3 | 243 |
| 2026-10-03 17:48 | alive | 639 ms | 3 | 243 |
Badge
[](https://mcp-pulse.ulehla.dev/s/com.findingleads/findingleads)