Skip to content

NextConstraint MCP server

app.nextconstraint/nextconstraintnextconstraint.appstreamable-httpv1.0.1Scanned

Your SaaS funnel's costliest leak, its fix, watchdog alerts and verdicts, from NextConstraint.

7 tools: 1 change things and 6 only read.

Tools: 0 delete, 0 irreversible, 1 write, 6 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the NextConstraint MCP server can do

The NextConstraint MCP server is published by nextconstraint.app, a domain the MCP Registry verified. It has 7 tools. It can create or change data (1 tool: mark_fix_done), but cannot delete data. 6 tools only read.

2 tools bring in text other people can write (list_alerts and get_fix_prompt).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 1Claude Code: ask
  • mark_fix_doneRecord that a fix has shipped: the current constraint's fix (omit issue_id) or one alert's fix.No findings

    Why it is in this group

    • The name "mark_fix_done" says "mark": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Mark fix shipped
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 6Show 6 read-only tools
  • 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 c…No findings

    Why it is in this group

    • The name "get_alert" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Alert detail
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • 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…No findings

    Why it is in this group

    • The name "get_current_constraint" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Current constraint
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • 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.Reads text others writeNo findings

    Why it is in this group

    • The name "get_fix_prompt" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "issue": it reads issues, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Fix prompt
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • 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…No findings

    Why it is in this group

    • The name "get_history" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: History
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • 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, t…No findings

    Why it is in this group

    • The name "get_status" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Funnel status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_alertsWatchdog alerts: open issues, plus those closed or fixed in the last 30 days, most expensive first.Reads text others writeNo findings

    Why it is in this group

    • The name "list_alerts" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "issue": it reads issues, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Alerts
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:21 UTC, unchanged since Nov 14, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://nextconstraint.app/mcp: tools/list returned 7 tools to an anonymous client, including mark_fix_done (write)

    What this check looks for

Posture changes

  1. Nov 14, 2026
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 1
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 1 (and 2 more).View diff
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 1
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http nextconstraint https://nextconstraint.app/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http nextconstraint https://nextconstraint.app/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__nextconstraint__get_status",
      "mcp__nextconstraint__get_current_constraint",
      "mcp__nextconstraint__list_alerts",
      "mcp__nextconstraint__get_alert",
      "mcp__nextconstraint__get_fix_prompt",
      "mcp__nextconstraint__get_history"
    ],
    "ask": [
      "mcp__nextconstraint__mark_fix_done"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as nextconstraint. Review it before you use it.

Capability tags behind 2 rules
  • mcp__nextconstraint__list_alerts untrusted-input
  • mcp__nextconstraint__get_fix_prompt untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/app.nextconstraint/nextconstraint/verify?hash=6f1b006955d8064bd359cfa46b174c1d53ae39ba5437a969685af1aef7b34132" | jq -e '.changed == false'

Pinned hash 6f1b006955d8, from Nov 13, 2026, 07:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/app.nextconstraint/nextconstraint/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for app.nextconstraint/nextconstraint
[![Anlyon Radar](https://radar.anlyon.com/badge/app.nextconstraint/nextconstraint.svg)](https://radar.anlyon.com/servers/app.nextconstraint/nextconstraint)

Source: MCP Registry. Synced Nov 13, 2026, 07:17 UTC.

NextConstraint MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the NextConstraint MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the NextConstraint MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the NextConstraint MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the NextConstraint MCP server have?

7 tools: 1 write, 6 read. mark_fix_done, get_status, get_current_constraint, list_alerts, get_alert, get_fix_prompt and get_history.

Does the NextConstraint MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the NextConstraint MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the NextConstraint MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.