Koskamo

Lasso MCP

An official MCP server by Lasso that allows AI agents to audit affiliate link health, identify revenue opportunities, track performance metrics, and perform dry-run audits on monetization without requiring manual intervention.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

Lasso MCP logo, by LassoVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-11-06Operated by Lasso
You need:Create a free Lasso account
MCP endpoint (Streamable HTTP)
https://lasso.link/mcp
Vendor documentation

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to getlasso.co ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Find broken links and out-of-stock products
  • Identify higher commission opportunities
  • Audit articles for missing monetization
  • Track click performance data

Source and maintenance

Vendor evidenceRegistry 1.0.0

Protocol and capabilities

Server
lasso 1.0.0
MCP protocol negotiated in check
2024-11-05
Tools
Sign-in required
Resources
Not advertised
Resource templates
Not advertised
Prompts
Sign-in required
Server-advertised capabilities
{
  "tools": {},
  "prompts": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Lasso MCP — customer vocabulary (use these phrases with creators; API field names in parentheses): - Brand Deals / Marketplace (Affiliate+, Aff+, affplus, aff_plus): Lasso-negotiated higher commission on eligible Amazon products. - Primary Destination URL (hop, hop_url, partner hop): Where the click lands after Lasso tracking. - hop_class affplus: Brand Deals / Marketplace hop. - hop_class associates: Amazon Associates / Amazon tracking ID (base Amazon affiliate tagging). - hop_class none / unmonetized: Plain Amazon link (not monetized yet) — no Brand Deal and no Associates tracking on that destination. - under-monetized: Earning the lower / base rate; eligible for a Brand Deal upgrade. - customer-owned hop: Link or program the creator set on purpose (Impact, ShareASale, etc.) — do not change. - opportunity (apply_opportunity): Brand Deal / Marketplace upgrade suggestion — not Hub keyword-monetize opportunities. - dry_run / Preview: Nothing saved until the creator confirms. Speak in customer phrases first; mention API aliases only when mapping tool receipts or parameters.

Tools

Sign-in required

No tool definitions available.

Prompts

Sign-in required

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (2 of 2 answered).

  1. 2026-11-06: 1 of 1 checks answered
  2. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
449 ms
95th percentile latency
449 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 449 ms · metadata changed · refuses unauthenticated tools/list (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http lasso-mcp https://lasso.link/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add lasso-mcp --url https://lasso.link/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable lasso-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "lasso-mcp": {
      "url": "https://lasso.link/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "lasso-mcp": {
      "type": "streamableHttp",
      "url": "https://lasso.link/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start lasso-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "lasso-mcp": {
      "type": "http",
      "url": "https://lasso.link/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http lasso-mcp https://lasso.link/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://lasso.link/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "lasso-mcp": {
      "serverUrl": "https://lasso.link/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Lasso MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run Lasso MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing