Lead Leak Check

io.github.paopao-studio-aiPublished by GitHub account paopao-studio-aiv0.1.0Updated Oct 30, 2026

Finds where inbound leads are silently dropped in Zapier, Make and n8n pipelines. Offline.

The publisher's own server: check.tattoo: tattoo size and placement guide

Overview

AI-generated overview

Offline MCP server that audits Zapier, Make or n8n lead pipelines and returns a ranked list of where inbound leads get silently dropped.

What you can do
  • Check a pipeline from a JSON config of sources, storage, routing, response and monitoring, returning a 0-100 risk score with findings ranked high, medium, low or verify
  • Check a pipeline described in plain English and get the same report plus how the text was interpreted
  • Analyze a CSV export of run history to surface failed and filtered runs, long gaps with no runs and stale workflows
  • Read the built-in rules resource listing all 15 leak rules with explanations and fixes
When to use it
Useful when you run lead capture through Zapier, Make or n8n and suspect leads are lost between first touch and first human reply, or when you want a quick risk review of a pipeline before or after changing it.
Requirements
Runs locally over stdio. Install from source with Python 3.10+ and pip, or use the MCPB bundle, which needs uv. No accounts, API keys or environment variables are declared, and it makes no network calls.
Before you install
You paste pipeline configuration, plain-English descriptions and run-history CSV exports into the assistant, so review them for customer data first. Findings are advisory: anything not described is marked verify, not safe. The README also advertises a paid consulting service and a free external template, which are unrelated to the tool itself.

Installation

In SourceWeft

  1. Open Lead Leak Check in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

lead-leak-check (MCP server)

Find where inbound leads are silently dropped between the first touch and the first human reply.

Your Zapier, Make or n8n runs say Success. The lead still never hears back: nobody owned the reply, a filter stopped on an empty field, the workflow was switched off for a day, or an AI draft sat unsent. lead-leak-check turns a description of your lead pipeline into a ranked list of those risks, each with a concrete fix.

Tools

ToolInputOutput
check_pipelineJSON config of your pipeline (sources, storage, routing, response, monitoring…)Risk score 0–100 and findings ranked high / medium / low / verify
check_pipeline_descriptionPlain English, e.g. "Typeform and WhatsApp go to Google Sheets via Zapier, nobody is assigned"Same report, plus how the text was interpreted
analyze_run_historyCSV export of run history (status column, optional timestamp)Failed and filtered runs, long gaps with no runs, stale workflows

Resource: leakcheck://rules lists all 15 rules with their explanation and fix.

Anything you don't describe is reported as verify, never as safe. No network calls, no data leaves your machine.

Install

bash
git clone https://github.com/paopao-studio-ai/lead-leak-check-mcp && cd lead-leak-check-mcppip install .            # Python 3.10+, works with mcp 1.x and 2.x

One-click bundle (MCPB)

Download lead-leak-check-mcp-0.1.0.mcpb from the latest release and open it in Claude Desktop (or any MCPB-aware client). Needs uv; dependencies install automatically.

Claude Desktop / Cursor / any MCP client

json
{  "mcpServers": {    "lead-leak-check": { "command": "lead-leak-check-mcp" }  }}

Without installing: {"command": "python", "args": ["-m", "lead_leak_check.server"], "env": {"PYTHONPATH": "/path/to/lead-leak-check-mcp/src"}}

Command line

bash
lead-leak-check check examples/pipeline.jsonlead-leak-check describe "WhatsApp leads land in Google Sheets via Make.com. Nobody is assigned."lead-leak-check history examples/run_history.csv --interval 30lead-leak-check --json check examples/pipeline.json

Config shape (all keys optional)

json
{  "name": "Typeform -> Google Sheets -> Slack #sales",  "sources": [{ "type": "web_form", "required_contact_field": false }, { "type": "whatsapp", "logged_to_storage": false }],  "storage": { "type": "google_sheets", "dedupe": false },  "routing": { "owner_assignment": "none", "after_hours_coverage": false },  "response": { "sla_minutes": 30, "auto_ack": true, "ai_drafts": true, "human_send_step": false },  "monitoring": { "error_alerts": false, "unanswered_lead_alert": false, "run_history_review": "never" },  "automation": { "platform": "zapier", "plan": "free" },  "timezone": { "business_tz": "America/New_York", "automation_tz": "UTC" },  "follow_up": { "sequence": false }}

Example output (top of the report for the config above):

# Lead leak risk: Typeform -> Google Sheets -> Slack #salesRisk score: **100/100** (12 findings)## 1. [HIGH] Nobody owns the first reply- Why it leaks: Leads posted to a shared sheet or channel are seen by everyone and answered by no one.- Fix: Assign an owner per lead (round robin or fixed) at the moment it is created, and name them in the notification.

Fix the #1 finding for free

The most common high-severity finding is "no alert when a lead goes unanswered". The free n8n missed-lead heartbeat template (https://github.com/paopao-studio-ai/n8n-missed-lead-heartbeat) checks your sheet or CRM every 5 minutes and pings Slack, Discord or any webhook when a lead waits past your SLA.

Want a human to map it?

Paopao Studio runs a fixed-price Lead Leak Check ($197): a written leak map of 1–2 lead workflows, credited in full to a Starter build within 30 days. Free screenshot triage by email. → https://paopao-studio.pages.dev/?utm_source=github&utm_medium=oss&utm_campaign=lead_leak_1029

Develop

bash
pip install -e ".[test]"pytest -q          # rule tests + an end-to-end stdio round trip with the official MCP client

License

MIT, see LICENSE.

Source: README.md at commit db77d71

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

1
  1. v0.1.0LatestOct 29, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Check integrations