nextconstraint

endpoint

https://nextconstraint.app/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is nextconstraint live?

Yes — it answered the hub's last check (checked 16h ago). It answered 100% of checks over the last 30 days.

Is nextconstraint free to use?

Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.

What tools does nextconstraint have?

7 tools: get_status, get_current_constraint, list_alerts, mark_fix_done, get_history, get_fix_prompt, get_alert.

Is nextconstraint safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• get_status auth-required never probed

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 lines copy
• get_current_constraint auth-required 16h ago

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 lines copy
• list_alerts auth-required 43h ago

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 lines copy
• mark_fix_done auth-required never probed

  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.

  mcp-tool

  123456789101112131415161718192021

  {
    "type": "object",
    "properties": {
      "branch": {
        "type": "string",
        "maxLength": 100,
        "description": "Optional: the branch the commit is on, for reference only (not matched against)."
      },
      "issue_id": {
        "type": "string",
        "format": "uuid",
        "description": "An alert id from list_alerts. Omit to mark the current constraint's fix."
      },
      "commit_sha": {
        "type": "string",
        "pattern": "^[0-9a-fA-F]{7,40}$",
        "description": "The git commit that contains the fix. Wait for it to reach a production deploy before the re-check starts, instead of starting immediately."
      }
    },
    "additionalProperties": false
  }

  arguments 21 lines copy
• get_history auth-required 16h ago

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 lines copy
• get_fix_prompt auth-required 16h ago

  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.

  mcp-tool

  12345678910111213141516171819202122

  {
    "type": "object",
    "properties": {
      "tool": {
        "enum": [
          "claude_code",
          "cursor",
          "lovable",
          "chatgpt"
        ],
        "type": "string",
        "default": "claude_code",
        "description": "Which coding tool the prompt is for."
      },
      "issue_id": {
        "type": "string",
        "format": "uuid",
        "description": "An alert id from list_alerts. Omit for the current constraint."
      }
    },
    "additionalProperties": false
  }

  arguments 22 lines copy
• get_alert auth-required never probed

  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.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "required": [
      "issue_id"
    ],
    "properties": {
      "issue_id": {
        "type": "string",
        "format": "uuid",
        "description": "An alert id from list_alerts."
      }
    },
    "additionalProperties": false
  }

  arguments 14 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.