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.

io.github.yumaheymans/bestrobotmower-mcp

REMOTE · BESTROBOTMOWER.CO

Robot lawn mower dataset from BestRobotMower.co: specs, prices, 0-5 scores, buying recommendations.

0 this week 88 Trust /100

Last scanned (14 hours ago)

Scores higher than 95% of remote servers

Reachable. Last reached 21 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 Security80
  • 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
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 522 tokens (~130/item across 4 items; 4 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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.

  • 19 Nov 26 0
    • “list_robot_mowers” reworded the description of “limit” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 14 Nov 26 +7
    • Authorization: unverified → partial ▲ security
    • Tool “compare_robot_mowers” now declares an output schema ▲ functional
    • Tool “get_robot_mower” now declares an output schema ▲ functional
    • Tool “list_robot_mowers” now declares an output schema ▲ functional
    • Tool “recommend_robot_mower” now declares an output schema ▲ functional
    • First check of Tool coverage: 100 functional
  • 13 Nov 26 0
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 12 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • Stability: pass → 0.97 functional
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 21 Nov 2026 · Probed https://bestrobotmower.co/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=bestrobotmower.co CN=YR2,O=Let's Encrypt,C=US 14 Oct 2026 12 Jan 2027 RSA 2048 SHA256-RSA 61558f9d849d034bde58391f7f41f21fa8d
SANs: bestrobotmower.co
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of bestrobotmower.co. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
co. DS published 7786 8 Verified
bestrobotmower.co. 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://platform.twitter.com https://www.googletagmanager.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https:; media-src 'self' https: blob:; font-src 'self' https://fonts.gstatic.com; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.stripe.com https://*.google-analytics.com https://*.analytics.google.com https://www.googletagmanager.com; worker-src 'self' blob:; frame-src 'self' https://js.stripe.com https://hooks.stripe.com https://www.youtube-nocookie.com https://www.youtube.com https://player.vimeo.com https://www.loom.com https://www.dailymotion.com https://platform.twitter.com; frame-ancestors 'self' http://localhost:* https://o-mega.ai https://*.o-mega.ai https://founden.ai https://*.founden.ai https://*.founden.co https://*.e2b.app https://*.vercel.app; object-src 'none'; base-uri 'self'
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), browsing-topics=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://bestrobotmower.co/api/mcp Verified 200
http (plaintext) http://bestrobotmower.co/api/mcp HTTPS enforced 308 https://bestrobotmower.co/api/mcp
MCP tools · 4 exposed · ~522 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
compare_robot_mowers ~73

Compare 2 to 5 robot lawn mowers side by side across navigation, coverage, slope, cutting specs, price and the 0-5 BestRobotMower Score. Pass each model by name or slug.

NameTypeReqDescription
modelsarrayyes2 to 5 model names or slugs to compare.
NameTypeReqDescription
attributionstringyes–
comparednumberyes–
licensestringyes–
missingarrayyesQueries that matched no model in the dataset.
resultsarrayyes–

No examples provided.

get_robot_mower ~79

Get the full specs, dated price, 0-5 score and sub-scores for a single robot lawn mower by name or slug (e.g. 'Mammotion Luba 2 AWD', 'Segway Navimow i110').

NameTypeReqDescription
querystringyesModel name, brand + model, or slug to look up.
NameTypeReqDescription
attributionstringyes–
available_modelsarray––
foundbooleanyes–
licensestringyes–
messagestring––
modelobject––
querystring––

No examples provided.

list_robot_mowers ~240

List and filter the robot lawn mowers in the BestRobotMower.co dataset by brand, navigation type, price, lawn-area coverage, slope handling and score. Returns models ranked by the 0-5 BestRobotMower Score (highest first).

NameTypeReqDescription
brandstring–Filter by brand, case-insensitive substring (e.g. 'Mammotion', 'Segway', 'Husqvarna').
limitinteger–Max models to return (default 10, max 78, the whole catalog).
max_price_usdnumber–Only models at or below this USD price.
min_lawn_area_m2number–Only models that cover at least this lawn area in square metres.
min_scorenumber–Only models with a BestRobotMower Score at or above this value (0-5).
min_slope_pctnumber–Only models rated for at least this slope, in percent grade.
navigationstring–Filter by navigation type, case-insensitive substring (e.g. 'RTK', 'satellite', 'vision', 'wire').
NameTypeReqDescription
attributionstringyes–
countnumberyesHow many models match the filters.
licensestringyes–
resultsarrayyes–
returnednumberyes–

No examples provided.

recommend_robot_mower ~130

Recommend the best robot lawn mowers for a specific yard: give the lawn area in square metres and optionally the steepest slope (percent grade) and a budget in USD. Returns up to 3 models that fit, ranked by the 0-5 BestRobotMower Score, with the reason each was chosen.

NameTypeReqDescription
budget_usdnumber–Maximum budget in USD (optional).
lawn_area_m2numberyesLawn area to mow, in square metres.
max_slope_pctnumber–Steepest slope on the lawn, in percent grade (optional).
NameTypeReqDescription
attributionstringyes–
licensestringyes–
notesarrayyesWhere the answer had to relax the request (coverage, budget or stock).
recommendationsarrayyes–
requestobjectyes–

No examples provided.

Install

How do I install the io.github.yumaheymans/bestrobotmower-mcp server?

io.github.yumaheymans/bestrobotmower-mcp is a hosted endpoint at https://bestrobotmower.co/api/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 · bestrobotmower.co

# add to Claude Code
claude mcp add --transport http yumaheymans-bestrobotmower-mcp 'https://bestrobotmower.co/api/mcp'
Common questions

What is the io.github.yumaheymans/bestrobotmower-mcp server?

io.github.yumaheymans/bestrobotmower-mcp is listed in the public MCP registry as io.github.yumaheymans/bestrobotmower-mcp. Robot lawn mower dataset from BestRobotMower.co: specs, prices, 0-5 scores, buying recommendations. This page covers its hosted endpoint (https://bestrobotmower.co/api/mcp).

Is the io.github.yumaheymans/bestrobotmower-mcp server safe to use?

io.github.yumaheymans/bestrobotmower-mcp scores 88 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 io.github.yumaheymans/bestrobotmower-mcp server expose?

io.github.yumaheymans/bestrobotmower-mcp exposes 4 tools: list_robot_mowers, get_robot_mower, compare_robot_mowers, recommend_robot_mower. Their descriptions and schemas cost roughly 522 tokens of context every time the server is loaded.

Does the io.github.yumaheymans/bestrobotmower-mcp server require authentication?

No. We connected to io.github.yumaheymans/bestrobotmower-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.yumaheymans/bestrobotmower-mcp server still maintained?

io.github.yumaheymans/bestrobotmower-mcp is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.yumaheymans/bestrobotmower-mcp server?

VerifyMCP ran 13 checks on io.github.yumaheymans/bestrobotmower-mcp, 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.