app.nextconstraintPublished by nextconstraint.appOfficial publisherv1.0.0Updated Nov 7, 2026
Your SaaS funnel's costliest leak, its fix, watchdog alerts and verdicts, from NextConstraint.
NextConstraint exposes a SaaS funnel's costliest leak, its prescribed fix, watchdog alerts and fix verdicts to an assistant.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/app.nextconstraint%2Fnextconstraint/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"nextconstraint": {
"type": "http",
"url": "https://nextconstraint.app/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Funnel status
Funnel health right now: whether a constraint is locked and where its re-check stands, every funnel step priced in dollars per month (only while nothing is locked - while one is, the rest is re-priced once it resolves), what each watchdog check concluded, and which sources are connected. Start here.
Takes no parameters.
Current constraint
The locked constraint: which funnel step is leaking, what it cost per month when it was selected, the one fix NextConstraint prescribed (and any prep step), and how the fix will be measured. Returns state "none" when nothing is locked.
Takes no parameters.
Alerts
Watchdog alerts: open issues, plus those closed or fixed in the last 30 days, most expensive first. Each has an id for get_alert, get_fix_prompt and mark_fix_done.
Takes no parameters.
Alert detail
One watchdog alert in full: what moved and by how much, what it costs if it continues, the likely causes lined up against the days before it started (deploys, price changes, page changes, traffic-source shifts - possible, not certain), and what could not be checked.
issue_idrequiredFix prompt
A ready-to-use fix prompt, written by NextConstraint, for the current constraint (omit issue_id) or for one alert, in the format for the chosen coding tool. It carries the evidence, the task, safety rules (new branch, show the diff, never touch billing, auth, user data or secrets) and how to check the fix worked. After shipping, call mark_fix_done with the commit SHA (see the fix-workflow prompt) rather than just marking it done.
toolissue_idHistory
Past constraints, newest first (up to 20): the leak, the fix tried, and how it ended - measured as better, no clear change or worse (with before and after), skipped as already done, dismissed, or not enough data.
Takes no parameters.
Mark fix shipped
Record that a fix has shipped: the current constraint's fix (omit issue_id) or one alert's fix. Give commit_sha (and optionally branch) when the fix was a code change: NextConstraint waits for that exact commit to reach a production deploy before starting the re-check, so the window starts from when the fix actually went live, not from this call (see the fix-workflow prompt). Omit commit_sha to start the re-check immediately instead - this only changes NextConstraint's own record and never touches the founder's code, payments or analytics. There is no undo here, so confirm with the founder that the fix is live (or, with a SHA, that it has been merged and will deploy) first.
branchissue_idcommit_sha83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.