# Getlasso [Verified owner] [Health: Active]

**Category:** 🛒 E-Commerce  
**Repository:** https://getlasso.co/mcp/  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mcp-218

## Description
Weekly health (H3), find OOS (H1), Aff+ upgrades without stomping owned hops (H8).

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: medium). Install path inferred — verify against the README before running it. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "getlasso": {
    "url": "https://getlasso.co/mcp/"
  }
}
```

## Documentation

## What Getlasso MCP server does

Getlasso MCP server is listed for three operational tasks: checking weekly health, finding OOS items, and upgrading affiliate links without stomping owned hops. The available description presents these tasks using the labels H3, H1, and H8 respectively.

The affiliate-upgrade behavior has one explicit constraint: owned hops should not be overwritten. That distinction matters when deciding whether this server fits an automation workflow that updates affiliate destinations or related link data. The listing does not explain how ownership is identified, what data is changed, or whether upgrades require approval.

For a developer evaluating fit, the clearest supported use is task-oriented automation around Getlasso’s described workflows. Getlasso MCP server may be relevant if an agent needs to perform or coordinate weekly health checks, locate OOS entries, or apply affiliate upgrades while preserving owned hops. The source does not provide enough detail to identify the underlying API, data store, account scope, or result format.

## Limitations and notes

As a result, the Getlasso MCP server’s installation procedure, transport, authentication model, environment variables, tool names, parameters, return values, error behavior, and permissions are undocumented here. No client-specific instructions are provided either.

The description also does not state whether the three listed tasks are separate MCP tools, prompts, resources, or higher-level workflows. It is therefore not possible to confirm exact invocation syntax or determine whether the server can run unattended. The phrase “weekly health” indicates a recurring health-oriented task, but scheduling support is not documented.

Before adopting Getlasso MCP server, confirm the supported MCP transport and the credentials it requires from the project’s own documentation. Test the OOS workflow against representative data, and verify that affiliate upgrades preserve owned hops as expected. Also confirm what “health” covers and how the server reports failures or skipped updates. These checks are necessary because the available listing establishes the intended task areas, not the implementation details.

_Full upstream README: https://allmcps.com/mcp/mcp-218/readme_