# Lagsmith (npm · lagsmith-mcp)

Let AI agents slow down, break or mock one app's network on a Mac, including iOS Simulator apps.

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

## Components

- npm · `lagsmith-mcp`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-lagsmith-mcp/lagsmith-mcp.md), [page](https://verifymcp.io/servers/com-lagsmith-mcp/lagsmith-mcp)

## Channel facts

- Registry: `npm`
- Package: `lagsmith-mcp`
- Version: `1.0.1`
- 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-21.

- **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**: 45/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).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1678 tokens (~167/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "clear_endpoints" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Lagsmith MCP server?

Lagsmith runs locally as an npm package, launched with npx -y lagsmith-mcp. 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 com-lagsmith-mcp -- npx -y lagsmith-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-lagsmith-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "lagsmith-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-lagsmith-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "lagsmith-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-lagsmith-mcp -- npx -y lagsmith-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-lagsmith-mcp --command npx --arg -y --arg lagsmith-mcp
```

### Hermes

```yaml
mcp_servers:
  com-lagsmith-mcp:
    command: "npx"
    args: ["-y", "lagsmith-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-lagsmith-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "lagsmith-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-lagsmith-mcp -t stdio -c npx -a -y lagsmith-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-lagsmith-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "lagsmith-mcp"
      ]
    }
  }
}
```

## 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-21 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 68, +1)

- [functional] Package version: 1.0.0 → 1.0.1

### 2026-11-16 (score 67)

First indexed and scored.

## MCP tools (10)

### `list_targets` (~31 tokens)

List running simulators and the apps installed on them, running Mac apps, the presets, and the current rules.

### `status` (~25 tokens)

Show every rule, what it's doing, and whether Lagsmith's proxy is running.

### `set_network` (~361 tokens)

Slow down or break one app's network, and only that app's. Creates the rule if needed and turns it on. Combine a preset with exact values or a failure mode.

Input parameters:

- `after` (number): For drop: seconds before a connection is cut.
- `app` (string, required): The app: a bundle ID like com.me.MyApp, an app name, or * for every app in a simulator.
- `down` (number): Download bandwidth in kilobits per second.
- `failure` (string): airplane: every connection fails at once. refuse: refuse a percent of new connections. timeout: connections never answer. drop: cut connections after some seconds. outages: go offline and back repeat…
- `hosts` (string): Comma-separated hosts to limit the rule to, like api.me.com,*.cdn.me.com.
- `hosts_mode` (string): only (default): just those hosts; except: everything but them.
- `jitter` (number): Latency variation in milliseconds.
- `latency` (number): Added latency in milliseconds.
- `loss` (number): Packet loss percent, 0 to 100.
- `offline` (number): For outages: seconds offline.
- `online` (number): For outages: seconds online.
- `percent` (number): For refuse: the percent of connections refused.
- `preset` (string): No Throttling, Edge, 3G, DSL, LTE, WiFi, Very Bad Network, 100% Loss, or a saved preset.
- `simulator` (string): For iOS Simulator apps: booted, any, a device name or a UDID. Leave out for a Mac app.
- `up` (number): Upload bandwidth in kilobits per second.

### `reset_network` (~98 tokens)

Put an app back to full speed with no failures, host limits or endpoint rules. It stays watched, so its requests still show.

Input parameters:

- `app` (string, required): The app: a bundle ID like com.me.MyApp, an app name, or * for every app in a simulator.
- `simulator` (string): For iOS Simulator apps: booted, any, a device name or a UDID. Leave out for a Mac app.

### `stop_watching` (~90 tokens)

Turn off an app's rule. Its traffic goes back to normal and stops being watched.

Input parameters:

- `app` (string, required): The app: a bundle ID like com.me.MyApp, an app name, or * for every app in a simulator.
- `simulator` (string): For iOS Simulator apps: booted, any, a device name or a UDID. Leave out for a Mac app.

### `relaunch_app` (~112 tokens)

Quit and reopen a simulator app with request monitoring, so every connection it makes goes through its rule and its requests are recorded. Do this after the first set_network for an app that was already running.

Input parameters:

- `app` (string, required): The app: a bundle ID like com.me.MyApp, an app name, or * for every app in a simulator.
- `simulator` (string, required): For iOS Simulator apps: booted, any, a device name or a UDID. Leave out for a Mac app.

### `get_requests` (~194 tokens)

A simulator app's recent HTTP requests, newest first: method, URL, status, errors, time, and optionally bodies. Needs the app to have been launched with request monitoring (relaunch_app).

Input parameters:

- `app` (string, required): The app: a bundle ID like com.me.MyApp, an app name, or * for every app in a simulator.
- `filter` (string): A search: words, or filters like status:4xx, method:POST, host:api, path:/v1, is:failed, -host:cdn.
- `include_bodies` (boolean): Include request and response bodies (up to 4,000 characters each).
- `limit` (integer): How many, 1 to 500. Default 50.
- `simulator` (string, required): For iOS Simulator apps: booted, any, a device name or a UDID. Leave out for a Mac app.

### `fail_endpoint` (~183 tokens)

Make requests to one endpoint fail inside a simulator app while the rest of the app works.

Input parameters:

- `app` (string, required): The app: a bundle ID like com.me.MyApp, an app name, or * for every app in a simulator.
- `kind` (string, required): offline: fails as no internet. timeout: times out. status: answers with an HTTP status. delay: sent after a wait.
- `pattern` (string, required): Requests whose URL contains this, like api.me.com/v1/feed. Use * for any text.
- `simulator` (string, required): For iOS Simulator apps: booted, any, a device name or a UDID. Leave out for a Mac app.
- `value` (number): For status: the HTTP status (default 500). For delay: seconds (default 3). For timeout: at most this many seconds.

### `mock_endpoint` (~166 tokens)

Answer requests to one endpoint in a simulator app with a made-up response, without reaching the server.

Input parameters:

- `app` (string, required): The app: a bundle ID like com.me.MyApp, an app name, or * for every app in a simulator.
- `body` (string): The response body, usually JSON.
- `content_type` (string): Default application/json.
- `delay` (number): Seconds to wait before answering.
- `pattern` (string, required): Requests whose URL contains this, like api.me.com/v1/user. Use * for any text.
- `simulator` (string, required): For iOS Simulator apps: booted, any, a device name or a UDID. Leave out for a Mac app.
- `status` (integer): HTTP status. Default 200.

### `clear_endpoints` (~104 tokens)

Remove an app's endpoint failures and mocks: all of them, or those for one pattern.

Input parameters:

- `app` (string, required): The app: a bundle ID like com.me.MyApp, an app name, or * for every app in a simulator.
- `pattern` (string): Only remove rules for this pattern.
- `simulator` (string): For iOS Simulator apps: booted, any, a device name or a UDID. Leave out for a Mac app.

## Diagnostics

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

## Score history

- 2026-11-21: 70
- 2026-11-20: 69
- 2026-11-19: 69
- 2026-11-18: 68
- 2026-11-17: 68
- 2026-11-16: 67

## Common questions

### What is the Lagsmith MCP server?

Lagsmith is an MCP server listed in the public MCP registry as com.lagsmith/mcp. Let AI agents slow down, break or mock one app's network on a Mac, including iOS Simulator apps. This page covers its npm package (lagsmith-mcp).

### Is the Lagsmith MCP server safe to use?

Lagsmith scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 Lagsmith MCP server expose?

Lagsmith exposes 10 tools: list_targets, status, set_network, reset_network, stop_watching, and 5 more. Their descriptions and schemas cost roughly 1,364 tokens of context every time the server is loaded.

### Is the Lagsmith MCP server still maintained?

Lagsmith is still listed as active in the MCP registry. We last reached this channel on 21 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 Lagsmith MCP server under?

Lagsmith declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Lagsmith MCP server?

VerifyMCP ran 16 checks on Lagsmith, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/lagsmith-mcp
- Socket report: https://socket.dev/npm/package/lagsmith-mcp
- Repository: https://github.com/lagsmith/lagsmith-mcp
- Website: https://lagsmith.com/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-lagsmith-mcp/lagsmith-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-lagsmith-mcp/lagsmith-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-lagsmith-mcp/lagsmith-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-lagsmith-mcp/lagsmith-mcp
