Lagsmith
NPM · LAGSMITH-MCP
Let AI agents slow down, break or mock one app's network on a Mac, including iOS Simulator apps.
Available components
Last scanned (13 hours ago)
Scores higher than 41% of npm servers
Category Testing and QA
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 & Transparency45
- 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
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +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.
- 19 Nov 26 +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.
- 17 Nov 26 +1
- Package version: 1.0.0 → 1.0.1 functional
- 16 Nov 26 67
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 21 Nov 2026 · Analysed npm/lagsmith-mcp@1.0.1
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 →
clear_endpoints ~104
Remove an app's endpoint failures and mocks: all of them, or those for one pattern.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | 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. |
No output schema declared.
No examples provided.
fail_endpoint ~183
Make requests to one endpoint fail inside a simulator app while the rest of the app works.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | The app: a bundle ID like com.me.MyApp, an app name, or * for every app in a simulator. |
| kind | string | yes | offline: fails as no internet. timeout: times out. status: answers with an HTTP status. delay: sent after a wait. |
| pattern | string | yes | Requests whose URL contains this, like api.me.com/v1/feed. Use * for any text. |
| simulator | string | yes | 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. |
No output schema declared.
No examples provided.
get_requests ~194
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).
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | 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 | yes | For iOS Simulator apps: booted, any, a device name or a UDID. Leave out for a Mac app. |
No output schema declared.
No examples provided.
list_targets ~31
List running simulators and the apps installed on them, running Mac apps, the presets, and the current rules.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mock_endpoint ~166
Answer requests to one endpoint in a simulator app with a made-up response, without reaching the server.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | 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 | yes | Requests whose URL contains this, like api.me.com/v1/user. Use * for any text. |
| simulator | string | yes | For iOS Simulator apps: booted, any, a device name or a UDID. Leave out for a Mac app. |
| status | integer | – | HTTP status. Default 200. |
No output schema declared.
No examples provided.
relaunch_app ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | The app: a bundle ID like com.me.MyApp, an app name, or * for every app in a simulator. |
| simulator | string | yes | For iOS Simulator apps: booted, any, a device name or a UDID. Leave out for a Mac app. |
No output schema declared.
No examples provided.
reset_network ~98
Put an app back to full speed with no failures, host limits or endpoint rules. It stays watched, so its requests still show.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | 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. |
No output schema declared.
No examples provided.
set_network ~361
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.
| Name | Type | Req | Description |
|---|---|---|---|
| after | number | – | For drop: seconds before a connection is cut. |
| app | string | yes | 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. |
No output schema declared.
No examples provided.
status ~25
Show every rule, what it's doing, and whether Lagsmith's proxy is running.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
stop_watching ~90
Turn off an app's rule. Its traffic goes back to normal and stops being watched.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | 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. |
No output schema declared.
No examples provided.
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.
npm · lagsmith-mcp
claude mcp add com-lagsmith-mcp -- npx -y lagsmith-mcp
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.