Getlasso

co.getlassoPublished by getlasso.cov1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote Getlasso MCP endpoint that lets an assistant run weekly health checks, find out-of-stock items and plan affiliate upgrades for a website.

What you can do
  • Run a weekly health check (H3) on a site.
  • Find out-of-stock items (OOS, H1).
  • Plan affiliate upgrades (Aff+) that do not overwrite owned hops (H8).
  • No tool list is published, so the exact operations are not documented.
When to use it
Worth adding if you manage affiliate or monetized websites through Getlasso and want an assistant to check site health, spot out-of-stock links and propose affiliate upgrades without disturbing existing owned hops.
Requirements
A remote streamable HTTP endpoint at lasso.link; no local package. Authentication is required: an Authorization header carrying a bearer token plus a Hub Website license key from the Getlasso websites dashboard.
Before you install
The Authorization header combines a bearer token with a license key, so treat it as a secret. The description mentions upgrades and changes to hops, so the assistant may modify affiliate link configuration; confirm before applying changes. The published description is very terse and no tool list is given, so scope is hard to verify in advance.

Installation

In SourceWeft

  1. Open Getlasso in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/co.getlasso%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "getlasso": {
      "type": "http",
      "url": "https://lasso.link/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.