Log inSubmit server
G

Getlasso

Checks weekly health, finds OOS items, and upgrades affiliate links without replacing owned hops.

InstallWebsite
Full README Compare alternatives Embed widget

Install Getlasso

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://getlasso.co/mcp/

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Overview

Getlasso MCP server appears to expose workflows for weekly health checks, finding OOS items, and upgrading affiliate links. Its listing specifically describes affiliate upgrades that avoid overwriting owned hops. Reach for it when an agent needs to handle these Getlasso tasks, but verify setup and client support because no README is available.

Use cases

  • Run weekly health checks
  • Find OOS items
  • Upgrade affiliate links
  • Preserve owned hops during upgrades

Key features

  • Weekly health checks
  • OOS item discovery
  • Affiliate link upgrades
  • Owned-hop preservation

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

13/13 checks healthy over the last 79d

How Getlasso works

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.

Read the full README

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Getlasso

Getlasso is an MCP server that connects AI agents to Getlasso workflows for weekly health checks, finding out-of-stock items, and upgrading affiliate links without overwriting owned hops.

The README is unavailable, so transport, commands, authentication, and configuration requirements must be confirmed in the project’s own documentation.

No client-specific setup instructions or standard MCP transport details are provided, so compatibility should be verified with the project before use.

Getlasso is listed as supporting an OOS-finding task.

Yes, preserving owned hops is an explicit constraint of the listed affiliate-upgrade workflow.

Related MCP servers

All in E-Commerce All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGetlasso AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-218?style=directory)](https://allmcps.com/mcp/mcp-218)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-218"><img src="https://allmcps.com/api/badge/mcp-218?style=directory" alt="Getlasso on AllMCPs" /></a>