io.github.GillMacedo/lapsewatch
NPM · LAPSEWATCH
Find customers who stopped buying, and the revenue at risk, from an orders CSV on your machine.
Available components
Last scanned (10 hours ago)
Scores higher than 42% of npm servers
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 248 tokens (~124/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 57
First indexed and scored.
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 5 Nov 2026 · Analysed npm/lapsewatch@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
customers_check_lapsed Find customers who stopped buying ~192
Finds at-risk and lost customers in an orders CSV by comparing each customer with their own buying pattern, with yearly revenue at risk, repeat rate and revenue concentration. Use for customer retention, churn analysis, or win-back lists. Read-only, and never uses the network. Results include customer names or emails from the file, so they reach the model. It can't contact anyone.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Date to measure from, YYYY-MM-DD. Default is the newest order |
| columns | object | – | Column names by field (date, customer, amount), when detection fails |
| date_format | string | – | dmy or mdy, needed only if the tool reports that dates are ambiguous |
| limit | null|integer | – | Most customers to return, highest priority first, default 100. 0 returns only the summary |
| path | string | yes | Path to the orders CSV |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | – |
| at_risk_yearly_value | string | yes | – |
| counts | object | yes | – |
| customers | integer | yes | – |
| customers_by_priority | null|array | yes | – |
| repeat_rate_percent | number | yes | – |
| revenue | string | yes | – |
| skipped_rows | null|array | yes | – |
| top_10_percent_revenue_share | number | yes | – |
| truncated | boolean | yes | – |
No examples provided.
customers_inspect_csv Inspect an orders CSV ~56
Shows which columns lapsewatch detects in an orders CSV and how many rows it can read, without returning row contents. Use if the file is unfamiliar or a check failed.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path to the orders CSV |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | object | yes | – |
| orders | integer | yes | – |
| skipped | integer | yes | – |
No examples provided.
How do I install the io.github.GillMacedo/lapsewatch MCP server?
io.github.GillMacedo/lapsewatch runs locally as an npm package, launched with npx -y lapsewatch. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · lapsewatch
claude mcp add gillmacedo-lapsewatch -- npx -y lapsewatch
What is the io.github.GillMacedo/lapsewatch MCP server?
io.github.GillMacedo/lapsewatch is an MCP server listed in the public MCP registry as io.github.GillMacedo/lapsewatch. Find customers who stopped buying, and the revenue at risk, from an orders CSV on your machine. This page covers its npm package (lapsewatch).
Is the io.github.GillMacedo/lapsewatch MCP server safe to use?
io.github.GillMacedo/lapsewatch scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.GillMacedo/lapsewatch MCP server expose?
io.github.GillMacedo/lapsewatch exposes 2 tools: customers_check_lapsed, customers_inspect_csv. Their descriptions and schemas cost roughly 248 tokens of context every time the server is loaded.
Is the io.github.GillMacedo/lapsewatch MCP server still maintained?
io.github.GillMacedo/lapsewatch is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.GillMacedo/lapsewatch MCP server under?
io.github.GillMacedo/lapsewatch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.