Productivity

stackcut.io

Provides tools to search and retrieve replacement recipes, find alternatives to paid products, and rank replacement paths by savings, payback, and popularity.

1 endpoint12 known toolsFirst detected September 25, 2026Last detected September 25, 2026

ENDPOINT 1

https://stackcut.io/mcp

No auth detected

MCP server metadata

Name: stackcut
Version: 1.2.0

Capabilities

tools

Server instructions

Stackcut maps SaaS subscriptions to cheaper ways to get the same job done. If the user has a Stackcut plan, they can give you a read-only agent code (sca_…): get_my_plan returns every line with its proof and steps; walk them through it from the biggest proven saving down and ask before any cancel or purchase. When they are choosing what to build with (best database, host, email service, cheapest way to build X), use choose_stack with their volumes. To audit a codebase: get_detection_rules (apply locally; send only vendor and feature names, never code or secret values), then audit_stack with the services found and the prices the user gives. Otherwise start with find_alternatives when the user names a product they pay for (pass monthly_spend_usd and features_used when known), or search_recipes by feature or category. get_recipe gives costs, scope, checks, sources, how to leave the current vendor, step-by-step playbooks, and Stackcut's own test results where they exist; get_build_packet gives a spec a coding agent can build from. Savings are modeled from public prices, not guaranteed: say so, and confirm must-have features before recommending a switch.

Known tools 12

search_recipes

Search Stackcut's catalog of replacement recipes.

Inferred read-only

get_recipe

Full recipe: the features it covers, what is out of scope, checks to run before switching, and every replacement path with modeled first-year net savings, monthly costs, setup hours, maintenance, pros/cons, license notes and sources.

Inferred read-only

find_alternatives

Given a product the user pays for (and optionally what they pay per month and the features they use), return the ranked ways to replace it, re-costed against their actual monthly bill, with which of their features each path covers.

Potential side effects

get_build_packet

Agent-ready build packet for a recipe: SPEC.

Inferred read-only

leaderboard

Top replacement paths across the catalog: 'savings' ranks by modeled first-year net savings, 'payback' by months to recover setup cost, 'popular' by how often people and agents used them.

Inferred read-only

audit_stack

Audit the paid services a codebase or team uses.

Inferred read-only

get_detection_rules

Rules for finding paid services in a codebase locally: package names (npm, PyPI, RubyGems, Go), environment variable NAME patterns, config files, API hosts, and per-feature code patterns for about 100 vendors.

Inferred read-only

list_categories

Categories in the catalog with recipe counts and the best modeled first-year savings in each.

Inferred read-only

get_my_plan

Read the user's own Stackcut savings plan with the read-only agent code they copied from stackcut.

Inferred read-only

choose_stack

For a project being built or planned, compare vendors per job (database, auth, hosting, transactional email, analytics, error monitoring, storage, payments, LLM API, …) at the user's expected volume.

Potential side effects

list_stack_jobs

The jobs choose_stack can compare (database, auth, hosting, email, …) with how many vendors and open-source options each has.

Potential side effects

report_outcome

Anonymously count that a user picked, switched to, or reverted from a replacement path.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.stackcut]
url = "https://stackcut.io/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "stackcut": {
      "type": "http",
      "url": "https://stackcut.io/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: stackcut
Remote MCP URL: https://stackcut.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "stackcut": {
      "url": "https://stackcut.io/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "stackcut": {
      "type": "http",
      "url": "https://stackcut.io/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "stackcut",
  "transport": "streamable-http",
  "url": "https://stackcut.io/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.