Skip to content

MiniMindsLab MCP Tools

com.minimindslab.mcp/toolsmcp.minimindslab.comstreamable-httpv2026.11.21133149587Scanned

Deterministic MiniMindsLab utilities for AI agents over MCP.

17 tools: 1 do something that can't be undone, 14 change things and 2 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. 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 MiniMindsLab MCP Tools can do

The MiniMindsLab MCP Tools is published by mcp.minimindslab.com, a domain the MCP Registry verified. It has 17 tools. It can do things that cannot be undone, such as sending, paying or publishing (spreadsheet-merge-conflict-reconciler) and create or change data (14 tools: accessible-name-and-label-regression-diff, api-pagination-and-cursor-consistency-checker, conference-badge-readability-tester, css-stacking-context-and-paint-order-inspector and 10 more), but cannot delete data. 2 tools only read.

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

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

Its remote endpoint lists its tools without sign-in, and its tools changed 5 times since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 2026.11.21133149587.

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.

17 tools

Can't be undone 1Claude Code: ask
  • spreadsheet-merge-conflict-reconcilerTeams need to reconcile two spreadsheet versions and see what changed, what conflicts, and which rows or columns need manual review.1 finding

    Why it is in this group

    • The name "spreadsheet-merge-conflict-reconciler" says "merge": a word for a change that another call does not undo.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "spreadsheet-merge-conflict-reconciler" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "spreadsheet-merge-conflict-reconciler" says "merge": a word for a change that another call does not undo.

      What this check looks for
    Description, as the server wrote it
    Teams need to reconcile two spreadsheet versions and see what changed, what conflicts, and which rows or columns need manual review.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
Changes things 14Claude Code: ask
  • accessible-name-and-label-regression-diffTeams need to know when a code change silently breaks accessible names, labels, or descriptions on interactive elements.1 finding

    Why it is in this group

    • The name "accessible-name-and-label-regression-diff" says "label": 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 "accessible-name-and-label-regression-diff" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "accessible-name-and-label-regression-diff" says "label": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Teams need to know when a code change silently breaks accessible names, labels, or descriptions on interactive elements.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • api-pagination-and-cursor-consistency-checkerBackend and frontend teams need to confirm that paginated API response samples keep page, offset, and cursor behavior consistent across endpoints and edge cases.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
    Backend and frontend teams need to confirm that paginated API response samples keep page, offset, and cursor behavior consistent across endpoints and edge cases.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • conference-badge-readability-testerEstimates whether a name badge is readable at social distance and flags text that will likely feel too small or too crowded.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
    Estimates whether a name badge is readable at social distance and flags text that will likely feel too small or too crowded.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • css-stacking-context-and-paint-order-inspectorUI developers need to know why an element is behind another element, clipped unexpectedly, or trapped inside a stacking context.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
    UI developers need to know why an element is behind another element, clipped unexpectedly, or trapped inside a stacking context.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • css-stacking-context-inspectorFrontend developers need to understand why an element is visually hidden behind another even when z-index seems correct.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
    Frontend developers need to understand why an element is visually hidden behind another even when z-index seems correct.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • csv-date-and-time-format-drift-checkerData teams need to catch when timestamp columns silently shift formats, time zones, or null patterns between file drops.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
    Data teams need to catch when timestamp columns silently shift formats, time zones, or null patterns between file drops.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • html-duplicate-id-and-aria-reference-checkerDevelopers need to catch duplicate IDs and broken ARIA relationships that silently break accessibility and scripting.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
    Developers need to catch duplicate IDs and broken ARIA relationships that silently break accessibility and scripting.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • json-contract-compatibility-checkerDevelopers need to confirm that a sample API response still matches a contract, including required fields, type expectations, enum constraints, and unexpected shape changes.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
    Developers need to confirm that a sample API response still matches a contract, including required fields, type expectations, enum constraints, and unexpected shape changes.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • json-duplicate-key-and-ambiguous-path-detectorDuplicate keys in JSON can silently overwrite data and cause hard-to-find bugs in configs and payloads.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
    Duplicate keys in JSON can silently overwrite data and cause hard-to-find bugs in configs and payloads.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • json-patch-impact-previewAPI and data engineers need to know exactly what a JSON Patch sequence will do before applying it to production data or test fixtures.1 finding

    Why it is in this group

    • The name "json-patch-impact-preview" says "patch": 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 "json-patch-impact-preview" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "json-patch-impact-preview" says "patch": a word for a change.

      What this check looks for
    Description, as the server wrote it
    API and data engineers need to know exactly what a JSON Patch sequence will do before applying it to production data or test fixtures.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • json-schema-drift-impact-checkerAPI and frontend engineers need to know whether a JSON schema change will break real payloads, generated clients, or form bindings before they ship it.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
    API and frontend engineers need to know whether a JSON schema change will break real payloads, generated clients, or form bindings before they ship it.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • multipart-form-data-inspectorFrontend and API developers need to see exactly what a browser will send as multipart form data, because hidden controls, disabled fields, repeated names, and file inputs often cre…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
    Frontend and API developers need to see exactly what a browser will send as multipart form data, because hidden controls, disabled fields, repeated names, and file inputs often create payload mismatches.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • webhook-payload-shape-sanity-checkerDevelopers need to verify that webhook events preserve required fields, nesting, and array shapes across example payloads before wiring integrations.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
    Developers need to verify that webhook events preserve required fields, nesting, and array shapes across example payloads before wiring integrations.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • webhook-signature-canonicalization-inspectorAPI developers need to reproduce how a webhook provider canonicalizes headers and payloads when a signature mismatch occurs.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
    API developers need to reproduce how a webhook provider canonicalizes headers and payloads when a signature mismatch occurs.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • api-breaking-change-diff-viewerDevelopers need to know whether a new API contract breaks existing clients before they merge or publish it.No findings

    Why it is in this group

    • The name "api-breaking-change-diff-viewer" says "diff": a word for reading.
    Description, as the server wrote it
    Developers need to know whether a new API contract breaks existing clients before they merge or publish it.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • json-schema-vs-sample-payload-diff-checkerAPI builders need to see exactly where a sample payload violates a schema or where the schema does not describe real data.No findings

    Why it is in this group

    • The name "json-schema-vs-sample-payload-diff-checker" says "diff": a word for reading.
    Description, as the server wrote it
    API builders need to see exactly where a sample payload violates a schema or where the schema does not describe real data.

    Annotations the server declares

    • readOnlyHint: true
    • 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 20, 2026, 18:42 UTC, unchanged since Nov 20, 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
14
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
  • HighThe whole server

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

    Matched text

    https://mcp.minimindslab.com/mcp: tools/list returned 16 tools to an anonymous client, including spreadsheet-merge-conflict-reconciler (irreversible), accessible-name-and-label-regression-diff (write), api-pagination-and-cursor-consistency-checker (write), conference-badge-readability-tester (write), css-stacking-context-and-paint-order-inspector (write) and 9 more

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 12 to 14
  2. Nov 13, 2026
    • Tools that change things, listed without credentials: 11 to 12
  3. Oct 29, 2026
    • Tools that change things, listed without credentials: 10 to 11

Findings

Matches of fixed checks, with the text they matched.

3 warn
  • The server marks "accessible-name-and-label-regression-diff" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "accessible-name-and-label-regression-diff" says "label": a word for a change.

    What this check looks for
  • The server marks "json-patch-impact-preview" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "json-patch-impact-preview" says "patch": a word for a change.

    What this check looks for
  • The server marks "spreadsheet-merge-conflict-reconciler" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "spreadsheet-merge-conflict-reconciler" says "merge": a word for a change that another call does not undo.

    What this check looks for

History

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

  1. Tools1 added.+1 addedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 12 -> 14.View diff
    • Tools that change things, listed without credentials: 12 to 14
  3. Tools2 added.+2 addedView diff
  4. PostureRemote posture changed. Tools that change things, listed without credentials: 11 -> 12.View diff
    • Tools that change things, listed without credentials: 11 to 12
  5. Tools1 added.+1 addedView diff
  6. PostureRemote posture changed. Tools that change things, listed without credentials: 10 -> 11.View diff
    • Tools that change things, listed without credentials: 10 to 11
  7. Tools1 added.+1 addedView diff
  8. Tools1 added.+1 addedView diff

Install

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

claude mcp add --transport http tools https://mcp.minimindslab.com/mcp
claude mcp add --transport http tools https://mcp.minimindslab.com/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__tools__api-breaking-change-diff-viewer",
      "mcp__tools__json-schema-vs-sample-payload-diff-checker"
    ],
    "ask": [
      "mcp__tools__accessible-name-and-label-regression-diff",
      "mcp__tools__api-pagination-and-cursor-consistency-checker",
      "mcp__tools__conference-badge-readability-tester",
      "mcp__tools__css-stacking-context-and-paint-order-inspector",
      "mcp__tools__css-stacking-context-inspector",
      "mcp__tools__csv-date-and-time-format-drift-checker",
      "mcp__tools__html-duplicate-id-and-aria-reference-checker",
      "mcp__tools__json-contract-compatibility-checker",
      "mcp__tools__json-duplicate-key-and-ambiguous-path-detector",
      "mcp__tools__json-patch-impact-preview",
      "mcp__tools__json-schema-drift-impact-checker",
      "mcp__tools__multipart-form-data-inspector",
      "mcp__tools__spreadsheet-merge-conflict-reconciler",
      "mcp__tools__webhook-payload-shape-sanity-checker",
      "mcp__tools__webhook-signature-canonicalization-inspector"
    ],
    "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 tools. Review it before you use it.

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/com.minimindslab.mcp/tools/verify?hash=ffaec7c194497f01f023c4d5c3dd51ce15e3d3859a5b46c920e4f8e3158a7de9" | jq -e '.changed == false'

Pinned hash ffaec7c19449, from Nov 21, 2026, 14:18 UTC.

Watch

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

https://radar.anlyon.com/servers/com.minimindslab.mcp/tools/changes.xml

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

Badge

Anlyon Radar badge for com.minimindslab.mcp/tools
[![Anlyon Radar](https://radar.anlyon.com/badge/com.minimindslab.mcp/tools.svg)](https://radar.anlyon.com/servers/com.minimindslab.mcp/tools)

Source: MCP Registry. Synced Nov 21, 2026, 14:18 UTC.

MiniMindsLab MCP Tools: questions and answers

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

Is the MiniMindsLab MCP Tools safe?

No scan can promise that. What its definitions show: 17 tools, 15 of which can change, send or delete something, and 3 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 MiniMindsLab MCP Tools delete data?

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

Can the MiniMindsLab MCP Tools do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: spreadsheet-merge-conflict-reconciler.

What tools does the MiniMindsLab MCP Tools have?

17 tools: 1 irreversible, 14 write, 2 read. spreadsheet-merge-conflict-reconciler, accessible-name-and-label-regression-diff, api-pagination-and-cursor-consistency-checker, conference-badge-readability-tester, css-stacking-context-and-paint-order-inspector, css-stacking-context-inspector, csv-date-and-time-format-drift-checker, html-duplicate-id-and-aria-reference-checker and 9 more.

Does the MiniMindsLab MCP Tools need sign-in or OAuth?

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

Does the MiniMindsLab MCP Tools send data to outside services?

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

Has the MiniMindsLab MCP Tools changed its tools?

Yes, 5 times since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.