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。
託管服務按其提供方的條款使用，因此這裡不要求授權條款。此檢查項不計入百分比。