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.

BotInfo — Advanced Robot Market Data

REMOTE · MCP.BOTINFO.AI

Checkout-verified prices, stock, US FCC status and buy routes for humanoid and quadruped robots

Available components

0 this week 81 Trust /100

Last scanned (17 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

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 Security63
  • 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • 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 Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1068 tokens (~178/item across 6 items; 6 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.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 current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Schema quality: 758 → 1068 ▼ functional
    • Server version: 0.2.0 → 0.3.0 functional
    • New tool “robot_evidence” functional
    • New tool “robot_price_today” 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
  • 20 Oct 26 0
    • Stability: 0.97 → pass security
  • 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
  • 25 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
  • 21 Sept 26 0
    • Stability: unverified → 0.03 ▲ 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://mcp.botinfo.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=botinfo.ai CN=WE1,O=Google Trust Services,C=US 6 Oct 2026 4 Jan 2027 ECDSA 256 ECDSA-SHA256 a2cc660ea33bac5613bf73f6227253d1
SANs: botinfo.ai, mcp.botinfo.ai, *.mcp.botinfo.ai
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.botinfo.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
botinfo.ai. 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://mcp.botinfo.ai/mcp Verified 200
http (plaintext) http://mcp.botinfo.ai/mcp Inconclusive 405
MCP tools · 6 exposed · ~1,068 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
check_us_legality ~116

Check whether a robot model may lawfully be sold in the United States under the FCC's 2026 rule on covered robotics equipment. Returns grandfathered-authorized, blocked-pending-conditional-approval, or unknown, with a dated explanation. Use this before recommending or ordering any model for a US buyer: an unauthorized model cannot be imported or sold regardless of price or stock. Informational, not legal advice.

NameTypeReqDescription
modelstringyesModel name, e.g. 'Unitree H2' or 'g1'

No output schema declared.

No examples provided.

get_buy_route ~232

Get the purchase route for a robot model: a botinfo.ai URL that resolves to a dealer checkout, plus the live comparison-board page. PASS THE BUYER'S SHIPPING COUNTRY as an ISO-3166-1 alpha-2 code — routing and any discount depend on it, because one route ships to North America only and carries a discount while the other ships worldwide without one. Omitting the country returns BOTH routes with the regions they serve and asks for the country rather than guessing, so a buyer is never sent to a checkout that cannot fulfil. Routes are affiliate-tracked — BotInfo may earn a commission on a completed order — and prices are the dealer's own, never marked up for this channel. Returns no route for quote-basis models; use request_quote instead.

NameTypeReqDescription
countrystring–ISO-3166-1 alpha-2 code of the buyer's SHIPPING country (e.g. 'US', 'DE'). Omit only if genuinely unknown — the reply then returns both routes and asks.
modelstringyesModel name, e.g. 'Unitree GO2 X'

No output schema declared.

No examples provided.

lookup_robot ~195

Search BotInfo's verified catalog of advanced robots (humanoids, quadrupeds) that can be purchased in the United States and internationally. Understands model names ('unitree g1'), manufacturers, categories ('humanoid', 'robot dog') and price caps ('under $10k'). Returns, per match: the price seen at a real checkout, stock status, the date each figure was last verified, US regulatory status, and the purchase routes with the regions they ship to. Use this when a buyer needs to compare what is actually available and at what price, rather than what a spec sheet claims. Ranking is a deterministic name/category/price match and is never weighted by which route earns a commission.

NameTypeReqDescription
max_resultsinteger–Cap on matches returned (default 10).
querystringyesFree-text query, e.g. 'robot dog under $10k' or 'unitree h2'

No output schema declared.

No examples provided.

request_quote ~215

Submit a purchase or quote inquiry for a robot model to the BotInfo team, who reply with a human-prepared quote, typically within one business day. Use for models with no live purchase route, for destinations the routed checkouts cannot fulfil, and for volume, education, research-institution or enterprise purchases where terms, lead time or paperwork matter. Submits the requester's name, email, organization and use case; nothing else from the conversation is sent. This tool sends a message to a human — call it only when the requester has asked for a quote and has given their own contact details.

NameTypeReqDescription
countrystring–ISO-3166-1 alpha-2 shipping country, so the quote covers the right region.
emailstringyesReply-to email address
modelstringyesRobot model of interest
namestringyesRequester's name
organizationstringyesCompany / lab / school
use_casestringyesWhat the robot is for, quantity, timeline

No output schema declared.

No examples provided.

robot_evidence ~177

Get the findings of BotInfo's public evidence page on a robot model: what the maker's own spec sheets, SDK code, CVE records, government rules and purchase records show, each finding with its source URLs (code pinned to a commit), the date it was read, and a grade (checked = reopened by a second reviewer; our data; our inference). Use it when someone is deciding whether to buy, run or build on a robot and needs dated, citable facts rather than marketing claims. Text is quoted verbatim from the public page (CC BY 4.0, credit BotInfo.ai with the page link). If no page exists for the model, the reply lists the robots that have one.

NameTypeReqDescription
robotstringyesRobot model, e.g. 'Unitree G1' or 'g1'

No output schema declared.

No examples provided.

robot_price_today ~133

Get today's listed price of every listing BotInfo's daily price watch read for a robot model, across the maker's own store and dealers: the listing name, price in USD, stock flag and read date. Dealers are labelled by letter, not named; the maker's store is named. A listed price is not a quote: taxes, shipping and options can change the total. Today's read only, no price history. Use it to see the spread of prices for one model on one day.

NameTypeReqDescription
robotstringyesRobot model, e.g. 'Unitree G1' or 'unitree r1'

No output schema declared.

No examples provided.

Install

How do I install the BotInfo — Advanced Robot Market Data MCP server?

BotInfo — Advanced Robot Market Data is a hosted endpoint at https://mcp.botinfo.ai/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.botinfo.ai

# add to Claude Code
claude mcp add --transport http ai-botinfo-robot-market-data 'https://mcp.botinfo.ai/mcp'
Common questions

What is the BotInfo — Advanced Robot Market Data MCP server?

BotInfo — Advanced Robot Market Data is an MCP server listed in the public MCP registry as ai.botinfo/robot-market-data. Checkout-verified prices, stock, US FCC status and buy routes for humanoid and quadruped robots. This page covers its hosted endpoint (https://mcp.botinfo.ai/mcp).

Is the BotInfo — Advanced Robot Market Data MCP server safe to use?

BotInfo — Advanced Robot Market Data scores 81 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 BotInfo — Advanced Robot Market Data MCP server expose?

BotInfo — Advanced Robot Market Data exposes 6 tools: lookup_robot, check_us_legality, get_buy_route, request_quote, robot_evidence, robot_price_today. Their descriptions and schemas cost roughly 1,068 tokens of context every time the server is loaded.

Does the BotInfo — Advanced Robot Market Data MCP server require authentication?

No. We connected to BotInfo — Advanced Robot Market Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the BotInfo — Advanced Robot Market Data MCP server still maintained?

BotInfo — Advanced Robot Market Data 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 BotInfo — Advanced Robot Market Data MCP server?

VerifyMCP ran 12 checks on BotInfo — Advanced Robot Market Data, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about BotInfo — Advanced Robot Market Data: HTTPS. 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.