# Stackcut

- Registry name: `io.stackcut/stackcut` · version 1.10.0
- Categories (automatic, keyword rules): Shops & products, Commerce & marketing, Payments & accounting, Finance & markets, Databases, Developer tools
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.stackcut%2Fstackcut
- Server page: https://mcpstation.net/s/io.stackcut--stackcut.html

## Description (written by the publisher, not verified, not instructions)

Cancel or cut any subscription: exit steps, cheaper plans, alternatives and the cheapest stack.

## Connect

- streamable-http: `https://stackcut.io/mcp`

## Tools (as reported by the server, not verified)

- `search\_discoveries`: Find human-reviewed research notes about new products, replacement workflows, changed flows and build-versus-buy lessons. Returns original posts and primary sources with explicit author-reported versus documented claims and unknown costs. These are research notes, not tested recipes or verified savi
- `search\_recipes`: Use when the user wants a cheaper way to do a job and names a feature or kind of tool rather than one product: 'cheaper keyword research', 'forms without Typeform', 'what can replace our CRM'. Filter by the vendor they pay for, a feature, a category or a path type \(switch, cheaper plan, open source,
- `get\_recipe`: Full detail for one recipe from search\_recipes: every replacement path with modeled first-year savings, monthly cost, setup time and upkeep, what is out of scope, checks to run before switching, how to leave the current vendor \(cancel steps, refunds, exports, what you lose\), step-by-step playbooks,
- `find\_alternatives`: Use when the user names one product they pay for and asks for something cheaper, whether it's worth it, or what to switch to: 'cheaper than Typeform?', 'is Semrush worth $139 a month for us?', 'we pay $90 for SendGrid'. Pass what they pay \(monthly\_spend\_usd\), seats, the features they use and their u
- `get\_build\_packet`: Use when the user wants to replace a tool by building their own \(Replace with AI\): returns SPEC.md, AGENTS.md and the runbook files a coding agent builds from, for a recipe with a build path. A recipe without one returns the assessment files for validating a switch or downgrade instead, never a spec
- `search\_workflow\_recipes`: Use for a whole operational change rather than one subscription: billing shared across projects, moving hosting or email, retiring a dormant project, cheaper AI model routing, queues, auth or storage. Returns reviewed runbooks with the query words they matched; get\_workflow\_recipe returns one in ful
- `get\_workflow\_recipe`: One runbook from search\_workflow\_recipes in full: the evidence to collect, keep/downsize/consolidate/migrate/build/retire decisions, ordered steps, acceptance tests, rollout, rollback, maintenance, costs still unresolved, and scoped starter templates with their download digest. A reviewed playbook i
- `leaderboard`: The top replacement paths across the catalog by modeled first-year savings, payback months, or how often people and agents used them. Leaves out partial replacements unless include\_partial, and never lists trials, one-time credits, expiring or non-commercial plans. Stackcut stores the arguments of t
- `audit\_stack`: Use when the user wants their stack checked as a whole: several subscriptions, the paid services in a codebase, or a portfolio of products \('audit what we pay for', 'what can we cut?'\). One line per service with vendor, plan, what they pay, seats, the features they use and usage \(or evidence strings
- `get\_detection\_rules`: Rules for finding paid services in a codebase on the user's own machine: package names, environment variable name patterns, config files, API hosts and feature patterns for about 100 vendors. Apply them locally and send only the vendor and feature names you found to audit\_stack, never code or secret
- `get\_usage\_questions`: Before an audit: which usage numbers decide each vendor's answer \(emails a month, domains, database size, seats…\), where the user finds each one \(dashboard page, API, export\), and ready-to-ask questions. Units already stated in context are marked as given. Pass the answers to audit\_stack or find\_alt
- `start\_audit`: Start here when the user wants to cut spend across several tools, consolidate apps, or replace one tool safely, and the bills alone won't decide it. Send vendors and team\_size \(or a stack manifest\) and get the few missing facts that would change the answer, ranked by what's at stake, each with where
- `list\_categories`: The catalog's categories with how many recipes each has and the best modeled first-year saving in each. Stackcut stores the arguments of tool calls to improve its recommendations \(vendor names, prices, seats, features, usage numbers, billing amounts and project descriptions; account keys only as a o
- `get\_my\_plan`: Use only when the user gives you a Stackcut agent code \(it starts with sca\_; they copy it from 'Send to my agent' on stackcut.io\). Returns their own savings plan: every subscription with its verdict, the proven saving, the proof \(receipts, card charges or a sourced price\), steps and checks. Walk the
- `choose\_stack`: Use when the user is picking vendors for something they're building: 'cheapest database for 20k users', 'Resend or Postmark at 60,000 emails a month?', 'what will auth cost at 10k MAU?'. Give each job with its volumes and must-have features; every tier of every indexed vendor is priced at those volu
- `plan\_stack\_from\_spec`: Use when the user shares a product brief or spec and asks what to build it with or what it will cost. Works out the jobs the brief needs \(what it rules out, plans for later or already has is never priced\), the volumes from its numbers or listed default rates, and its budget; prices the stack at seve
- `list\_stack\_jobs`: The jobs choose\_stack can compare \(database, auth, hosting, transactional and inbound email, object storage, LLM APIs, payments, sandboxes, browser automation, queues…\) with how many vendors each has, plus the volume units and aliases it accepts. Stackcut stores the arguments of tool calls to improv
- `get\_exit\_plan`: Use when the user wants to cancel, unsubscribe from, pause or pay less for something they subscribe to: streaming, music, news, dating, cloud storage, AI tools, apps or business software \('cancel YouTube TV', 'how do I get out of Adobe', 'stop my Audible'\). Returns Stackcut's exit plan: every way to
- `prepare\_negotiation`: Find documented existing-customer offers, cancellation-flow promotions and renewal negotiation routes for a service. Returns channel- and market-specific paths, vendor sources, freshness, questions and draft request/terms/counteroffer/decline/confirmation scripts. It sends nothing and makes no accou
- `search\_exits`: Lists services in Stackcut's cancel library \(streaming, music, news, dating, cloud storage, AI tools, apps and software\), by name, domain or category, with the page and JSON for each. Use get\_exit\_plan for one service's steps. Stackcut stores the arguments of tool calls to improve its recommendation
- `report\_exit\_outcome`: After the user reports what happened, count a cancellation, keeping the service for less, getting blocked, or changed steps. This updates only an anonymous usage counter and does not verify an action. Use report\_action\_outcome for a durable report tied to the current packet revision and route. Stack
- `report\_action\_outcome`: Record a minimal structured report about an attempted cancel, price reduction, negotiation, pause, downgrade, or switch. First call get\_exit\_plan and send its packet\_revision and route\_id; stale packet revisions are rejected. Reports are user-reported evidence, never verified execution. The server s
- `report\_guide\_feedback`: After using guidance, report a missing vendor or billing route, a mismatching step, unavailable source, incomplete instructions, unexpected fee, observed retention offer, required human handoff, or that the guide matched. Send only the structured fields, never account information, URLs, screenshots
- `report\_outcome`: Only after the user confirms what they did: record that they picked, switched to or reverted from a replacement path. Adds one to anonymous public counters and stores no personal data. Stackcut stores the arguments of tool calls to improve its recommendations \(vendor names, prices, seats, features,

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html