# io.github.GillMacedo/lapsewatch (npm · lapsewatch)

Find customers who stopped buying, and the revenue at risk, from an orders CSV on your machine.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `lapsewatch`: 72/100 (this document), [markdown](https://verifymcp.io/servers/gillmacedo-lapsewatch/lapsewatch.md), [page](https://verifymcp.io/servers/gillmacedo-lapsewatch/lapsewatch)

## Channel facts

- Registry: `npm`
- Package: `lapsewatch`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 248 tokens (~124/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**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.

## Install

### 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.

### Claude

```bash
claude mcp add gillmacedo-lapsewatch -- npx -y lapsewatch
```

### Cursor

```json
{
  "mcpServers": {
    "gillmacedo-lapsewatch": {
      "command": "npx",
      "args": [
        "-y",
        "lapsewatch"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "gillmacedo-lapsewatch": {
      "command": "npx",
      "args": [
        "-y",
        "lapsewatch"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add gillmacedo-lapsewatch -- npx -y lapsewatch
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gillmacedo-lapsewatch": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "lapsewatch"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add gillmacedo-lapsewatch --command npx --arg -y --arg lapsewatch
```

### Hermes

```yaml
mcp_servers:
  gillmacedo-lapsewatch:
    command: "npx"
    args: ["-y", "lapsewatch"]
```

### Netclaw

```json
{
  "McpServers": {
    "gillmacedo-lapsewatch": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "lapsewatch"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add gillmacedo-lapsewatch -t stdio -c npx -a -y lapsewatch
```

### Other

```json
{
  "mcpServers": {
    "gillmacedo-lapsewatch": {
      "command": "npx",
      "args": [
        "-y",
        "lapsewatch"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-01 (score 72, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 57)

First indexed and scored.

## MCP tools (2)

### `customers_check_lapsed` (~192 tokens)

Find customers who stopped buying

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.

Input parameters:

- `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, required): Path to the orders CSV

Output parameters:

- `as_of` (string)
- `at_risk_yearly_value` (string)
- `counts` (object)
- `customers` (integer)
- `customers_by_priority` (null|array)
- `repeat_rate_percent` (number)
- `revenue` (string)
- `skipped_rows` (null|array)
- `top_10_percent_revenue_share` (number)
- `truncated` (boolean)

### `customers_inspect_csv` (~56 tokens)

Inspect an orders CSV

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.

Input parameters:

- `path` (string, required): Path to the orders CSV

Output parameters:

- `columns` (object)
- `orders` (integer)
- `skipped` (integer)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/gillmacedo-lapsewatch/lapsewatch#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 72
- 2026-11-03: 72
- 2026-11-02: 72
- 2026-11-01: 72
- 2026-10-31: 57

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/lapsewatch
- Socket report: https://socket.dev/npm/package/lapsewatch
- Repository: https://github.com/GillMacedo/lapsewatch
- Changelog RSS feed: https://verifymcp.io/servers/gillmacedo-lapsewatch/lapsewatch.xml
- Changelog JSON feed: https://verifymcp.io/servers/gillmacedo-lapsewatch/lapsewatch.json
- HTML version of this page: https://verifymcp.io/servers/gillmacedo-lapsewatch/lapsewatch