Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Mini Split Reef

REMOTE · MINISPLITREEF.COM

Austin TX mini splits at $2,000 each: prices, ZIP coverage, financing and quote requests.

0 this week 73 Trust /100

Last scanned (2 minutes ago)

Scores higher than 59% of remote servers

Reachable. Last reached 22 Nov 2026.

Category IoT and Hardware

Trust breakdown (7 categories)

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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 461 tokens (~92/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability check failed: schema churn in the 30 days we've observed: 4 tool removals, 0 breaking changes, 0 auth/transport breaks, 4 additions. See how to fix → Fail
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 0
    • Stability: pass → fail ▼ security
    • Tool “check_coverage” was removed ▼ security
    • Tool “estimate_job” was removed ▼ security
    • Tool “get_financing” was removed ▼ security
    • Tool “request_quote” was removed ▼ security
    • Authorization: unverified → partial ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_pricing” rewrote its description, which is the text the model reads security
    • Schema quality: 63 → 92 ▼ functional
    • Tool coverage: 9% → 100% ▲ functional
    • Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
    • Server version: 1.0.0 → 2.0.0 functional
    • New tool “ask_minisplit_reef” functional
    • New tool “get_contact” functional
    • New tool “get_service_details” functional
    • New tool “place_order” functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 3 Nov 26 0
    • Stability: 0.97 → pass security
  • 2 Nov 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.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 22 Nov 2026 · Probed https://minisplitreef.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=minisplitreef.com CN=YE1,O=Let's Encrypt,C=US 31 Oct 2026 29 Jan 2027 ECDSA 256 ECDSA-SHA384 600e18b424b679f6977c11c2d4e531bba4e
SANs: minisplitreef.com, www.minisplitreef.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of minisplitreef.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
minisplitreef.com. No DS 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://minisplitreef.com/mcp Verified 200
http (plaintext) http://minisplitreef.com/mcp HTTPS enforced 301 https://minisplitreef.com/mcp
MCP tools · 5 exposed · ~336 tokens

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 →

Tool Tokens
ask_minisplit_reef ~79

Ask any question about getting a mini split installed by Mini Split Reef (price, unit, warranty, timing, ordering). Answers come only from our posted facts; anything else gets 'contact us at info@minisplitreef.com'. Cannot look up existing orders.

NameTypeReqDescription
questionstringyesThe customer's question, in plain words

No output schema declared.

No examples provided.

get_contact ~31

How to reach Mini Split Reef: the email address to give the customer, the website, and how to order.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_pricing ~33

Mini Split Reef's posted installed price, the possible add-ons, the bring-your-own-unit price and the brand comparison.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_service_details ~36

The unit we install, how long the install takes, the warranty, what's included, how you can pay, and where we go.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

place_order ~157

Send the customer's mini split order to Mini Split Reef. Someone reaches out to confirm the details and set the install time; no payment is taken here. Only call this when the user asks to order and gives their OWN name, phone, email and address or city.

NameTypeReqDescription
address_or_citystringyesInstall address, or at least the city
detailsstringyesWhat they need: how many mini splits, which rooms, own unit or ours, anything else
emailstringyesCustomer's email address
namestringyesCustomer's full name
phonestringyesCustomer's US phone number
preferred_timestring–Preferred day or time for the install or a call back

No output schema declared.

No examples provided.

Install

How do I install the Mini Split Reef MCP server?

Mini Split Reef is a hosted endpoint at https://minisplitreef.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 · minisplitreef.com

# add to Claude Code
claude mcp add --transport http com-minisplitreef-mini-splits 'https://minisplitreef.com/mcp'
Common questions

What is the Mini Split Reef MCP server?

Mini Split Reef is an MCP server listed in the public MCP registry as com.minisplitreef/mini-splits. Austin TX mini splits at $2,000 each: prices, ZIP coverage, financing and quote requests. This page covers its hosted endpoint (https://minisplitreef.com/mcp).

Is the Mini Split Reef MCP server safe to use?

Mini Split Reef scores 73 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 Mini Split Reef MCP server expose?

Mini Split Reef exposes 5 tools: get_pricing, get_service_details, get_contact, ask_minisplit_reef, place_order. Their descriptions and schemas cost roughly 336 tokens of context every time the server is loaded.

Does the Mini Split Reef MCP server require authentication?

No. We connected to Mini Split Reef without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Mini Split Reef MCP server still maintained?

Mini Split Reef is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Mini Split Reef MCP server?

VerifyMCP ran 13 checks on Mini Split Reef, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.