INDIVIDUAL MCP TOOL
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.
LIVE ENDPOINT
https://stackcut.io/mcp
Connect to this endpoint to inspect the live schema for get_detection_rules and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
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.
Related tools
search_recipes— Search Stackcut's catalog of replacement recipes.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.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.get_build_packet— Agent-ready build packet for a recipe: SPEC.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.audit_stack— Audit the paid services a codebase or team uses.list_categories— Categories in the catalog with recipe counts and the best modeled first-year savings in each.get_my_plan— Read the user's own Stackcut savings plan with the read-only agent code they copied from stackcut.