Your SaaS funnel's costliest leak, its fix, watchdog alerts and verdicts, from NextConstraint.
Connect Remote server
claude mcp add --transport http nextconstraint https://nextconstraint.app/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"nextconstraint": {
"url": "https://nextconstraint.app/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"nextconstraint": {
"type": "http",
"url": "https://nextconstraint.app/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://nextconstraint.app/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools 7 found in our last check
get_statusFunnel 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 c…
get_current_constraintThe 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.
list_alertsWatchdog 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.
get_alertOne 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.
get_fix_promptA 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 secret…
get_historyPast 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_doneRecord 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 wi…
Headers
| Name | Description |
|---|---|
AuthorizationRequired, secret | "Bearer " followed by a NextConstraint MCP token (ncm_...), created in Settings > Connect your AI agent. |
Details
| Endpoint | https://nextconstraint.app/mcp (Streamable HTTP) |
| First published | 13 Nov 2026 |
| Last updated | 13 Nov 2026 |
| Registry name | app.nextconstraint/nextconstraint |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
