MiniMindsLab MCP Tools
REMOTE · MCP.MINIMINDSLAB.COM
Deterministic MiniMindsLab utilities for AI agents over MCP.
Available components
Last scanned (4 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2947 tokens (~226/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "spreadsheet-merge-conflict-reconciler" implies "merge" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Oct 26 0
- New tool “css-stacking-context-and-paint-order-inspector” functional
- 22 Oct 26 0
- Schema quality: 2477 → 2761 ▼ functional
- New tool “webhook-signature-canonicalization-inspector” functional
- 17 Oct 26 0
- Schema quality: 2193 → 2477 ▼ functional
- New tool “multipart-form-data-inspector” functional
- 6 Oct 26 0
- Stability: 0.97 → pass security
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 74
- Schema quality: 1967 → 2193 ▼ functional
- New tool “json-schema-drift-impact-checker” functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Schema quality: 1751 → 1967 ▼ functional
- New tool “api-pagination-and-cursor-consistency-checker” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.minimindslab.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=minimindslab.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | fd32c3090c1cb5ef13b4a57972b23dbc |
| SANs: minimindslab.com, *.minimindslab.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.minimindslab.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| minimindslab.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.minimindslab.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.minimindslab.com/mcp | HTTPS enforced | 308 | https://mcp.minimindslab.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
accessible-name-and-label-regression-diff Accessible Name and Label Regression Diff ~175
Teams need to know when a code change silently breaks accessible names, labels, or descriptions on interactive elements.
| Name | Type | Req | Description |
|---|---|---|---|
| include_description | boolean | yes | When true, compare accessible descriptions in addition to accessible names and labels. |
| match_by_selector | boolean | yes | When true, element matching prefers stable CSS-like selector identity when available; otherwise fallback matching is used. |
| new_dom_snippet | string | yes | Required. Must contain a non-empty HTML or DOM fragment. Plain text is treated as literal markup input, not rendered content. |
| old_dom_snippet | string | yes | Required. Must contain a non-empty HTML or DOM fragment. Plain text is treated as literal markup input, not rendered content. |
| show_element_paths | boolean | yes | When true, output includes deterministic element path strings for matched and problematic nodes. |
| Name | Type | Req | Description |
|---|---|---|---|
| accessibility_summary | object | – | – |
| ambiguous_elements | array | – | – |
| element_path_report | object | – | – |
| missing_label_list | array | – | – |
| regression_list | array | – | – |
No examples provided.
api-breaking-change-diff-viewer API Breaking Change Diff Viewer ~219
Developers need to know whether a new API contract breaks existing clients before they merge or publish it.
| Name | Type | Req | Description |
|---|---|---|---|
| ignore_additive_changes | boolean | yes | When true, do not include new optional fields, new array members in additive-only contexts, or other non-breaking additions in the visible change lists. |
| new_contract_json | string | yes | Must be valid JSON text representing the proposed contract version. The tool must reject empty input and invalid JSON with a parse error. |
| old_contract_json | string | yes | Must be valid JSON text representing the previous contract version. The tool must reject empty input and invalid JSON with a parse error. |
| show_path_details | boolean | yes | When true, include full normalized JSON paths for every finding. When false, keep messages concise while preserving path references in structured results. |
| strict_mode | boolean | yes | When true, treat type changes, removed required fields, removed paths, enum narrowing, and object-to-non-object changes as breaking. When false, still report them but additive changes may be separate… |
| Name | Type | Req | Description |
|---|---|---|---|
| breaking_changes | array | – | – |
| compatibility_status | string | – | – |
| compatibility_summary | object | – | – |
| enum_violations | array | – | – |
| missing_paths | array | – | – |
| non_breaking_changes | array | – | – |
| type_mismatch_paths | array | – | – |
No examples provided.
api-pagination-and-cursor-consistency-checker API Pagination and Cursor Consistency Checker ~216
Backend and frontend teams need to confirm that paginated API response samples keep page, offset, and cursor behavior consistent across endpoints and edge cases.
| Name | Type | Req | Description |
|---|---|---|---|
| page_size | number | – | Optional. If provided, must be a positive integer. Used to verify per-page item counts and boundary transitions. |
| pagination_mode | string | yes | Select the intended pagination contract. 'mixed' means samples may contain more than one pagination style and the checker will verify consistency within each style. |
| response_samples | string | yes | Must contain one or more API response samples in JSON text form. Each sample must parse as an object or array. Empty input is invalid. |
| show_item_paths | boolean | – | When true, output item path references for duplicates, gaps, and boundary findings when they can be inferred from the samples. |
| sort_key | string | – | Optional. If provided, must be a non-empty field path such as 'created_at' or 'data.items[].id'. Used as the expected stable ordering key across samples. |
| Name | Type | Req | Description |
|---|---|---|---|
| consistency_summary | string | – | – |
| duplicate_item_flags | array | – | – |
| missing_cursor_flags | array | – | – |
| page_boundary_report | object | – | – |
| pagination_status | string | – | – |
No examples provided.
conference-badge-readability-tester Conference Badge Readability Tester ~193
Estimates whether a name badge is readable at social distance and flags text that will likely feel too small or too crowded.
| Name | Type | Req | Description |
|---|---|---|---|
| badge_width_mm | number | yes | Must be a finite number between 20 and 300. Values outside the range are invalid. |
| company_text | string | yes | Text is required. Leading and trailing whitespace are trimmed. Empty after trimming is invalid. |
| font_size_pt | number | yes | Must be a finite number between 6 and 72. Non-numeric or out-of-range values are invalid. |
| name_text | string | yes | Text is required. Leading and trailing whitespace are trimmed. Empty after trimming is invalid. |
| role_text | string | – | Optional text. If provided, it is trimmed. Empty string is treated as blank. |
| viewing_distance_cm | number | yes | Must be a finite number between 20 and 500. Values outside the range are invalid. |
| Name | Type | Req | Description |
|---|---|---|---|
| badge_summary | object | – | – |
| crowding_warnings | array | – | – |
| line_break_suggestions | array | – | – |
| readability_score | number | – | – |
| sizing_notes | array | – | – |
No examples provided.
css-stacking-context-and-paint-order-inspector CSS Stacking Context and Paint Order Inspector ~186
UI developers need to know why an element is behind another element, clipped unexpectedly, or trapped inside a stacking context.
| Name | Type | Req | Description |
|---|---|---|---|
| css_snippet | string | yes | Must be a non-empty CSS text snippet. Ignore unsupported at-rules gracefully and continue parsing what can be understood. |
| html_snippet | string | yes | Must be a non-empty HTML text snippet. The tool must parse a static DOM tree from this input only. |
| selected_element | string | yes | Must identify exactly one element in the provided HTML. Accept a CSS selector or element path string. If it matches zero or multiple elements, return a selection error. |
| show_paint_order | boolean | yes | Boolean flag controlling whether the paint order trace is included in the result. |
| show_stacking_context_chain | boolean | yes | Boolean flag controlling whether the stacking context chain is included in the result. |
| Name | Type | Req | Description |
|---|---|---|---|
| clipping_and_containment_warnings | array | – | – |
| diagnostic_summary | object | – | – |
| layering_explanation | string | – | – |
| likely_fix_hints | array | – | – |
| paint_order_trace | array | – | – |
| stacking_context_chain | array | – | – |
No examples provided.
css-stacking-context-inspector CSS Stacking Context Inspector ~223
Frontend developers need to understand why an element is visually hidden behind another even when z-index seems correct.
| Name | Type | Req | Description |
|---|---|---|---|
| css_snippet | string | yes | Required. Must contain one or more CSS rules. Trim leading and trailing whitespace. If empty, show a validation error and do not compute results. |
| html_snippet | string | yes | Required. Must contain HTML markup for the inspected layout. Trim leading and trailing whitespace. If empty, show a validation error and do not compute results. |
| selected_element | string | yes | Required. Must be a CSS selector or element reference token that matches at least one element in the provided HTML snippet. If no match is found, return a selection error. |
| show_paint_order | boolean | yes | Boolean flag. When true, include a paint order trace. When false, omit the detailed trace but still compute the main layering explanation. |
| show_stacking_context_chain | boolean | yes | Boolean flag. When true, include the ancestry of stacking context creators from root to selected element. When false, include only the summarized cause. |
| Name | Type | Req | Description |
|---|---|---|---|
| clipping_and_containment_warnings | array | – | – |
| diagnostic_summary | object | – | – |
| layering_explanation | string | – | – |
| likely_fix_hints | array | – | – |
| paint_order_trace | array | – | – |
| stacking_context_chain | array | – | – |
No examples provided.
html-duplicate-id-and-aria-reference-checker HTML Duplicate ID and ARIA Reference Checker ~191
Developers need to catch duplicate IDs and broken ARIA relationships that silently break accessibility and scripting.
| Name | Type | Req | Description |
|---|---|---|---|
| check_aria_references | boolean | yes | When true, scan ARIA ID reference attributes and validate each referenced id against the parsed fragment. When false, aria-reference analysis is skipped and broken-reference outputs are empty. |
| check_duplicate_ids | boolean | yes | When true, report every duplicated id value with all matching element locations. When false, duplicate-id analysis is skipped and duplicate outputs are empty. |
| html_snippet | string | yes | Accept raw HTML or DOM snippet text. Must be non-empty after trimming. Parse as HTML fragment in document order. Script execution is never allowed. |
| show_element_paths | boolean | yes | When true, include stable element paths for duplicate and broken-reference findings. When false, path fields are omitted from per-finding detail but summary counts still compute. |
| Name | Type | Req | Description |
|---|---|---|---|
| broken_aria_references | array | – | – |
| duplicate_id_groups | array | – | – |
| element_path_report | array | – | – |
| missing_target_list | array | – | – |
| validation_status | object | – | – |
No examples provided.
json-contract-compatibility-checker JSON Contract Compatibility Checker ~243
Developers need to confirm that a sample API response still matches a contract, including required fields, type expectations, enum constraints, and unexpected shape changes.
| Name | Type | Req | Description |
|---|---|---|---|
| contract_json | string | yes | Must be valid JSON text. The contract must be an object. Supported contract keys are name/title, type, required, properties, items, enum, const, additionalProperties, and nested combinations of those… |
| sample_json | string | yes | Must be valid JSON text. The sample must be a JSON object, array, string, number, boolean, or null. Missing or invalid JSON must produce a parse error. |
| show_path_details | boolean | yes | When true, mismatch outputs must include explicit JSONPath-like paths such as $.user.name. When false, the report may summarize issues without omitting the required output lists. |
| strict_mode | boolean | yes | When true, extra paths not allowed by the contract are reported as mismatches whenever additionalProperties is false or omitted for object branches that define properties. When false, extra paths are… |
| Name | Type | Req | Description |
|---|---|---|---|
| compatibility_status | string | – | – |
| enum_violations | array | – | – |
| extra_paths | array | – | – |
| missing_paths | array | – | – |
| type_mismatch_paths | array | – | – |
No examples provided.
json-schema-drift-impact-checker JSON Schema Drift Impact Checker ~226
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.
| Name | Type | Req | Description |
|---|---|---|---|
| new_json_schema | string | yes | Must be valid JSON text representing the proposed schema version. The schema must parse as an object; if parsing fails, show a parse error and stop comparison. |
| old_json_schema | string | yes | Must be valid JSON text representing the previous schema version. The schema must parse as an object; if parsing fails, show a parse error and stop comparison. |
| sample_payloads | string | – | Optional JSON text. Accept a single JSON value, an array of JSON values, or newline-separated JSON values. Blank input means no sample payload analysis. |
| show_path_details | boolean | yes | Boolean toggle. When true, path-level findings must include explicit JSON Pointer style paths and short evidence notes. |
| strict_mode | boolean | yes | Boolean toggle. When true, treat any added required constraint, narrowed type, removed enum option, reduced allowed array/object shape, or newly forbidden property as breaking. |
| Name | Type | Req | Description |
|---|---|---|---|
| additive_changes | array | – | – |
| breaking_paths | array | – | – |
| compatibility_status | string | – | – |
| compatibility_summary | string | – | – |
| impact_summary | object | – | – |
| potentially_breaking_paths | array | – | – |
No examples provided.
json-schema-vs-sample-payload-diff-checker JSON Schema vs Sample Payload Diff Checker ~271
API builders need to see exactly where a sample payload violates a schema or where the schema does not describe real data.
| Name | Type | Req | Description |
|---|---|---|---|
| additional_properties_mode | string | yes | Controls handling of object properties not declared by the schema. schema_default uses the schema's own additionalProperties / unevaluatedProperties rules where supported by the tool. allow ignores e… |
| json_schema | string | yes | Must be valid JSON text representing a JSON Schema document. If parsing fails, show a schema parse error and skip comparison. |
| sample_json | string | yes | Must be valid JSON text representing an instance payload. If parsing fails, show a sample parse error and skip comparison. |
| show_paths | boolean | yes | When true, include JSON Pointer-style instance paths for every mismatch. When false, still compute paths internally but present concise grouped results. |
| strict_types | boolean | yes | When true, require exact JSON type matches for object, array, string, number, integer, boolean, and null. Integers must still be numbers with no fractional component. When false, permit only JSON Sch… |
| Name | Type | Req | Description |
|---|---|---|---|
| enum_violations | array | – | – |
| extra_property_paths | array | – | – |
| missing_field_paths | array | – | – |
| summary | object | – | – |
| type_mismatch_paths | array | – | – |
| validation_status | string | – | – |
No examples provided.
multipart-form-data-inspector Multipart Form Data Inspector ~284
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.
| Name | Type | Req | Description |
|---|---|---|---|
| control_state_overrides | string | yes | Must be valid JSON text describing per-control state overrides such as value, checked, selected, disabled, or files. If empty, treat as an empty object. Invalid JSON must produce a parse error state… |
| expected_field_list | string | yes | Must be a newline-separated or comma-separated list of expected field names, or an empty string. Names are compared case-sensitively and after trimming surrounding whitespace. |
| html_form_snippet | string | yes | Must contain a single HTML <form> snippet or a fragment that includes one form element. Empty input is invalid. The tool must parse markup locally only. |
| selected_submitter | string | yes | Must be a submit control identifier such as a control name, id, or CSS-like path token understood by the parser, or an empty string to indicate no explicit submitter. If the selector matches multiple… |
| submission_mode | string | yes | Must be one of the supported deterministic modes. multipart/form-data computes browser-like multipart serialization metadata and field ordering; form-data-preview-only suppresses boundary rendering w… |
| Name | Type | Req | Description |
|---|---|---|---|
| duplicate_field_flags | array | – | – |
| excluded_control_report | array | – | – |
| missing_fields | array | – | – |
| payload_mismatch_summary | object | – | – |
| submission_preview | object | – | – |
No examples provided.
spreadsheet-merge-conflict-reconciler Spreadsheet Merge Conflict Reconciler ~236
Teams need to reconcile two spreadsheet versions and see what changed, what conflicts, and which rows or columns need manual review.
| Name | Type | Req | Description |
|---|---|---|---|
| case_sensitive | boolean | yes | When false, row key matching and field comparisons ignore letter case. When true, comparisons preserve letter case exactly. |
| match_keys | string | yes | Provide one or more column names used to match rows between Sheet A and Sheet B. Separate multiple keys with commas, semicolons, or new lines. Each key must exist in both sheets after normalization. |
| sheet_a | string | yes | Paste or upload the first sheet snapshot as tabular text. Accept CSV-style or TSV-style rows with a header row. Must contain at least one data row and one header row. |
| sheet_b | string | yes | Paste or upload the second sheet snapshot as tabular text. Accept CSV-style or TSV-style rows with a header row. Must contain at least one data row and one header row. |
| trim_whitespace | boolean | yes | When true, leading and trailing whitespace is removed from headers, keys, and cell values before matching and comparison. Internal spaces are preserved. |
| Name | Type | Req | Description |
|---|---|---|---|
| added_rows | array | – | – |
| cell_differences | array | – | – |
| conflict_rows | array | – | – |
| reconciliation_summary | object | – | – |
| removed_rows | array | – | – |
No examples provided.
webhook-signature-canonicalization-inspector Webhook Signature Canonicalization Inspector ~284
API developers need to reproduce how a webhook provider canonicalizes headers and payloads when a signature mismatch occurs.
| Name | Type | Req | Description |
|---|---|---|---|
| body_text | string | yes | Accept the exact request body as plain text. Preserve all characters exactly as entered, including line breaks and trailing whitespace, before applying the selected signing rule mode. If empty, the b… |
| headers_text | string | yes | Accept raw HTTP header lines in plain text. Each non-empty line should be in the form Name: value. Leading and trailing whitespace around names and values is trimmed during parsing. Duplicate header… |
| secret_or_shared_key | string | yes | Accept the webhook signing secret or shared key as text. The tool must not mask, store, transmit, or auto-save it. Empty input is invalid. |
| signing_rule_mode | string | yes | Select one deterministic signing rule mode. The tool must apply the chosen rule exactly and must not infer undocumented provider-specific behavior outside the selected mode. |
| timestamp_tolerance | number | yes | Enter a non-negative whole number of seconds. Used only when the selected signing rule mode requires timestamp verification. Values above 86400 are invalid. A tolerance of 0 means only exact timestam… |
| Name | Type | Req | Description |
|---|---|---|---|
| canonical_request_preview | string | – | – |
| mismatch_explanation | string | – | – |
| replay_risk_flags | array | – | – |
| signature_diff_summary | object | – | – |
| verification_status | object | – | – |
No examples provided.
How do I install the MiniMindsLab MCP Tools server?
MiniMindsLab MCP Tools is a hosted endpoint at https://mcp.minimindslab.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.minimindslab.com
claude mcp add --transport http com-minimindslab-mcp-tools 'https://mcp.minimindslab.com/mcp'
What is the MiniMindsLab MCP Tools server?
MiniMindsLab MCP Tools is listed in the public MCP registry as com.minimindslab.mcp/tools. Deterministic MiniMindsLab utilities for AI agents over MCP. This page covers its hosted endpoint (https://mcp.minimindslab.com/mcp).
Is the MiniMindsLab MCP Tools server safe to use?
MiniMindsLab MCP Tools scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MiniMindsLab MCP Tools server expose?
MiniMindsLab MCP Tools exposes 13 tools: accessible-name-and-label-regression-diff, api-breaking-change-diff-viewer, api-pagination-and-cursor-consistency-checker, conference-badge-readability-tester, css-stacking-context-and-paint-order-inspector, and 8 more. Their descriptions and schemas cost roughly 2,947 tokens of context every time the server is loaded.
Does the MiniMindsLab MCP Tools server require authentication?
No. We connected to MiniMindsLab MCP Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MiniMindsLab MCP Tools server still maintained?
MiniMindsLab MCP Tools is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.