app.nextconstraint由 nextconstraint.app 发布官方发布者v1.0.0更新于 Nov 7, 2026
Your SaaS funnel's costliest leak, its fix, watchdog alerts and verdicts, from NextConstraint.
NextConstraint 让助手查看 SaaS 漏斗中代价最高的流失点、其指定修复方案、监控告警与修复结论。
Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/app.nextconstraint%2Fnextconstraint/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。把它添加到你客户端的 mcpServers 配置中。
{
"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.
无需输入参数。
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.
无需输入参数。
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.
无需输入参数。
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_id必填Fix 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.
无需输入参数。
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_sha已满足适用检查项的 83%
该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。
请声明包含 README 的 GitHub 仓库，或在 OAuth 受保护资源元数据中提供 resource_documentation。
托管服务按其提供方的条款使用，因此这里不要求许可证。此检查项不计入百分比。