mcp-pulse

com.leadfriendly/lead-friendly

Lead Friendly

com.leadfriendly/lead-friendly did not answer the probe on 2026-10-03. Result: needs auth (HTTP 401).

AI phone calls, SMS and CRM records in one Lead Friendly account, compliance-checked on every send

needs auth probed 2026-10-03 · HTTP 401 · Bearer

Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","id":null,"error":{"code":-32001,"message":"Unauthorized. Send Authorization: Bearer <your Le
Endpoint
https://www.leadfriendly.com/api/mcp/v1 (streamable-http)
Host
www.leadfriendly.com
Website
https://www.leadfriendly.com/mcp
Registry
active, updated 2026-09-25 · registry entry
Reachable
2 of the last 2 probes

History

We add a row when the result changes. A server with no change keeps its last row.

ProbedResultInitToolsTokens
2026-10-03 20:30needs auth
2026-10-03 17:48needs auth

Badge

mcp-pulse: needs auth

[![mcp-pulse](https://mcp-pulse.ulehla.dev/badge/com.leadfriendly/lead-friendly.svg)](https://mcp-pulse.ulehla.dev/s/com.leadfriendly/lead-friendly)