lassocut-mcp

MCPattested
v1.0.1JAUPIN Design LLCMITUpdated 5d agonpmGitHub

LassoCut background removal for AI assistants (MCP server): Claude Desktop, Claude Code, Cursor, Windsurf

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
322Downloads/wk
5d agoLast update
Reads these credentials
  • LASSOCUT_API_KEYAPI keyoptional

    Optional LassoCut API key (otherwise use the sign_in tool)

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorJAUPIN Design LLC
LicenseMIT
Version1.0.1
Sourcenpm+mcp-registry
npmlassocut-mcp
GitHubjaupin94/lassocut-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · dd2e904
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface3 tools · 1 privileged
Security scan✓ Cleanv1.0.1 · 2d agoHow well does this scan work?
EvalsNone
IndexedOct 1, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

3 tools · 1 privileged
Statically extracted from the published packagev1.0.1 · 2d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

remove_backgroundprivilegedRemove the background of images with LassoCut. Accepts file paths, folders (their images, not subfolders) or http(s) URLs, up to 50 per call. Saves '<name>-no-bg.<ext>' next to each original (or in output_dir) and never overwrites. Uses size 'preview' (0.25 credit, 50 free a month, up to 10 a day)…

Remove the background of images with LassoCut. Accepts file paths, folders (their images, not subfolders) or http(s) URLs, up to 50 per call. Saves '<name>-no-bg.<ext>' next to each original (or in output_dir) and never overwrites. Uses size 'preview' (0.25 credit, 50 free a month, up to 10 a day)…

No input schema was published for this tool.

get_creditsShow the LassoCut credit balance and the free previews available now (50 a month, up to 10 a day).

Show the LassoCut credit balance and the free previews available now (50 a month, up to 10 a day).

No input schema was published for this tool.

sign_inConnect a LassoCut account: opens the LassoCut approval page in the browser and returns right away with the URL and code. Approval is saved automatically in the background (up to 5 minutes); call get_credits afterwards to check. Use force: true to switch accounts.

Connect a LassoCut account: opens the LassoCut approval page in the browser and returns right away with the URL and code. Approval is saved automatically in the background (up to 5 minutes); call get_credits afterwards to check. Use force: true to switch accounts.

No input schema was published for this tool.

3 of 3 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

LassoCut background removal for AI assistants (MCP server): Claude Desktop, Claude Code, Cursor, Windsurf

Keywords
mcpmodel-context-protocolbackground-removalremove-backgroundclaudecursor
Alternatives
Comparing tool surfaces…

Tools exposed

3 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-02 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

8 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.