Is the NoBrainer Tech Flow MCP server safe?

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

Can the NoBrainer Tech Flow MCP server delete data?

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

Can the NoBrainer Tech Flow 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.

Does the NoBrainer Tech Flow MCP server need sign-in or OAuth?

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

Does the NoBrainer Tech Flow MCP server send data to outside services?

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

Has the NoBrainer Tech Flow MCP server changed its tools?

Not since anlyon.dev started tracking it. Last scanned Nov 10, 2026.

NoBrainer Tech Flow MCP server

io.github.nobrainer-tech/nobrainer-tech-flownobrainer-techstreamable-httpv2.12.0Scanned 5 days ago

Task contract, evidence check and done gate for AI coding agents. Read-only, no sign-in.

6 tools: 5 change things and 1 only read.

Reads private data · 0
Reads text others write · 0
Can send data out · 0
1 finding

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here change things. Govern them.

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.dev only lists and labels, and these labels are the same either way.

What the NoBrainer Tech Flow MCP server can do

The NoBrainer Tech Flow MCP server is published by the GitHub account nobrainer-tech. It has 6 tools. It can create or change data (5 tools: start_flow_task, check_flow_evidence, check_flow_done, draft_flow_handoff and 1 more), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 2.12.0.

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.

6 tools

Changes things 5Creates or changes something that can be changed back.Claude Code: ask

check_flow_doneUse before saying a task is done.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
Use before saying a task is done. Returns DONE only when every DoD item has accepted, current evidence, DONE_WITH_GAPS when the rest are listed in unchecked with a reason, otherwise NOT_DONE with the exact missing items.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
check_flow_evidenceUse after running a check.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
Use after running a check. Validates one to four evidence records against DoD items in the contract token: exit codes, test counts in the output, hashes, URL status and evidence level. It cannot see your machine; it checks structure and consistency only. Returns verdicts and an updated token.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
draft_flow_handoffUse after check_flow_done.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
Use after check_flow_done. Returns a short final-report skeleton from the done receipt: delivered outcome, proof per DoD item, what was not checked, decisions left to the user and the next action.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
recommend_flow_modelUse when picking a model for a Flow task: top-3 from a pinned NoBrainer benchmark snapshot, no invented scores.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
Use when picking a model for a Flow task: top-3 from a pinned NoBrainer benchmark snapshot, no invented scores.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
start_flow_taskUse at the start of a non-trivial task.1 finding
Why it is in this group
- The name "start_flow_task" says "start": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
  The server marks "start_flow_task" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
  Matched text
  annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "start_flow_task" says "start": a word for a change.
  What this check looks for
Description, as the server wrote it
Use at the start of a non-trivial task. Checks your proposed outcome and definition of done (DoD) against Flow's contract rules, chooses the quick or full path, and returns DoD item IDs, a signed contract token and the first step. Computes only; stores nothing. Save the token in your goal file.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false

Only reads 1Looks things up and changes nothing.Show 1 read-only tool

get_flow_stepUse when you need guidance on a Flow stage, an event (e.g.No findings
Why it is in this group
- The name "get_flow_step" says "get": a word for reading.
Description, as the server wrote it
Use when you need guidance on a Flow stage, an event (e.g. blocked), a module (e.g. nobrainer-review), or a PR's Definition of Done or readiness (topic pr_dod). Returns up to six rules quoted from the pinned release, with their source. With a token, event resume also returns a goal block.
Annotations the server declares
- 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 untrusted-input or outbound.

Reads private data0: Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0: 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 10, 2026, 08:20 UTC, unchanged since Nov 10, 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: 5
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 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
Matched text
https://mcp.nobrainer.tech/mcp: tools/list returned 6 tools to an anonymous client, including start_flow_task (write), check_flow_evidence (write), check_flow_done (write), draft_flow_handoff (write), recommend_flow_model (write)
What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn

Warnstart_flow_task
The server marks "start_flow_task" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
Matched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "start_flow_task" says "start": a word for a change.
What this check looks for

History

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

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

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

claude mcp add --transport http nobrainer-tech-flow https://mcp.nobrainer.tech/mcp

claude mcp add --transport http nobrainer-tech-flow https://mcp.nobrainer.tech/mcp

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__nobrainer-tech-flow__get_flow_step"
    ],
    "ask": [
      "mcp__nobrainer-tech-flow__start_flow_task",
      "mcp__nobrainer-tech-flow__check_flow_evidence",
      "mcp__nobrainer-tech-flow__check_flow_done",
      "mcp__nobrainer-tech-flow__draft_flow_handoff",
      "mcp__nobrainer-tech-flow__recommend_flow_model"
    ],
    "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 nobrainer-tech-flow. Review it before you use it.

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://anlyon.dev/api/v1/servers/io.github.nobrainer-tech/nobrainer-tech-flow/verify?hash=c064c92415e97494253336e33f575b5696ab7b98861747167b22fc8a662a6266" | jq -e '.changed == false'

Pinned hash c064c92415e9, from Nov 10, 2026, 01:18 UTC.

Watch

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

https://anlyon.dev/servers/io.github.nobrainer-tech/nobrainer-tech-flow/changes.xml

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

Badge

[![anlyon.dev](https://anlyon.dev/badge/io.github.nobrainer-tech/nobrainer-tech-flow.svg)](https://anlyon.dev/servers/io.github.nobrainer-tech/nobrainer-tech-flow)

Source: MCP Registry · repository. Synced Nov 10, 2026, 01:17 UTC.