
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
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.
Installation
In SourceWeft
- Open Lead Leak Check in the dashboard and add it to a workspace.
- 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
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
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
Without installing: {"command": "python", "args": ["-m", "lead_leak_check.server"], "env": {"PYTHONPATH": "/path/to/lead-leak-check-mcp/src"}}
Command line
Config shape (all keys optional)
Example output (top of the report for the config above):
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
License
MIT, see LICENSE.
Source: README.md at commit db77d71
Tools
0Version history
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
check.tattoo: tattoo size and placement guide
tattoo.checkOfficial publisher
check.tattoo: tattoo size and placement guide's hosted MCP server, published by check.tattoo; no sign-in required; Streamable HTTP; 5 tools.
iva.pt — EU VAT check (VIES) and Portuguese VAT law
pt.ivaOfficial publisher
Validates EU VAT numbers against VIES and returns Portuguese VAT Code (CIVA) and RITI articles, in Portuguese or English.

U.S. Public Company Check
Published by GitHub account JusticeUA
Remote Apify-hosted MCP server that lets an assistant look up U.S. public company checks by SEC CIK: filing status, bankruptcy 8-K flag, LEI and sanctions.

Taiwan Company Check
Published by GitHub account JusticeUA
Remote MCP server that lets an assistant look up Taiwanese companies by Unified Business Number for tax status, LEI and sanctions checks.

Romania Company Check
Published by GitHub account JusticeUA
Looks up Romanian companies by CUI, returning status, insolvency, LEI and sanctions data from official registers.