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.

Vuntum

REMOTE · VUNTUM.COM

Sourced, dated data on consumer robots and physical AI: specs, prices, availability, evidence.

Available components

+3 this week 80 Trust /100

Last scanned (18 hours ago)

Scores higher than 85% of remote servers

Reachable. Last reached 16 Oct 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 Security83
Transport & Reachability100
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1650 tokens (~103/item across 16 items; 16 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 79% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 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
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.

  • 15 Oct 26 +1

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

  • 13 Oct 26 +1

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

  • 12 Oct 26 +1

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

  • 9 Oct 26 +1

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

  • 7 Oct 26 +3
    • HSTS header: fail → pass ▲ security
    • Tool “find_robots_by_utility” rewrote its description, which is the text the model reads security
  • 6 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “compare_robots” rewrote its description, which is the text the model reads security
    • Tool “find_home_robots” rewrote its description, which is the text the model reads security
    • Tool “find_programmable_robots” rewrote its description, which is the text the model reads security
    • Tool “find_robots_by_capability” rewrote its description, which is the text the model reads security
    • Tool “find_robots_by_utility” rewrote its description, which is the text the model reads security
    • Tool “get_article” rewrote its description, which is the text the model reads security
    • Tool “get_methodology” rewrote its description, which is the text the model reads security
    • Tool “get_recent_changes” rewrote its description, which is the text the model reads security
    • Tool “get_robot” rewrote its description, which is the text the model reads security
    • Tool “get_robot_availability” rewrote its description, which is the text the model reads security
    • Tool “get_robot_claims” rewrote its description, which is the text the model reads security
    • Tool “get_robot_prices” rewrote its description, which is the text the model reads security
    • Tool “get_robot_sources” rewrote its description, which is the text the model reads security
    • Tool “search_open_source_projects” rewrote its description, which is the text the model reads security
    • Tool “search_robots” rewrote its description, which is the text the model reads security
    • Tool “search_site” rewrote its description, which is the text the model reads security
    • Schema quality: 73 → 103 ▼ functional
    • Tool coverage: 70% → 79% ▲ functional
    • Stability: unverified → 0.07 ▲ functional
    • “find_home_robots” added an optional parameter “locale” cosmetic
    • “find_programmable_robots” added an optional parameter “locale” cosmetic
    • “find_robots_by_capability” added an optional parameter “locale” cosmetic
    • “find_robots_by_utility” added an optional parameter “locale” cosmetic
    • “get_methodology” added an optional parameter “locale” cosmetic
    • “get_recent_changes” added an optional parameter “locale” cosmetic
    • “get_robot_availability” added an optional parameter “locale” cosmetic
    • “get_robot_claims” added an optional parameter “locale” cosmetic
    • “get_robot_prices” added an optional parameter “locale” cosmetic
    • “get_robot_sources” added an optional parameter “locale” cosmetic
    • “search_open_source_projects” added an optional parameter “locale” cosmetic
    • “get_robot_sources” reworded the description of “slug” cosmetic
    • “compare_robots” reworded the description of “locale” cosmetic
    • “find_home_robots” reworded the description of “limit” cosmetic
    • “find_programmable_robots” reworded the description of “limit” cosmetic
    • “find_robots_by_capability” reworded the description of “limit” cosmetic
    • “find_robots_by_utility” reworded the description of “limit” cosmetic
    • “get_article” reworded the description of “locale” cosmetic
    • “get_article” reworded the description of “slug” cosmetic
    • “get_recent_changes” reworded the description of “limit” cosmetic
    • “get_robot” reworded the description of “locale” cosmetic
    • “get_robot” reworded the description of “slug” cosmetic
    • “get_robot_availability” reworded the description of “slug” cosmetic
    • “get_robot_claims” reworded the description of “slug” cosmetic
    • “get_robot_prices” reworded the description of “slug” cosmetic
    • “search_open_source_projects” reworded the description of “limit” cosmetic
    • “search_robots” reworded the description of “limit” cosmetic
    • “search_robots” reworded the description of “locale” cosmetic
    • “search_site” reworded the description of “limit” cosmetic
    • “search_site” reworded the description of “locale” cosmetic
    • Tool “compare_robots” changed its title: Comparer des robots → Compare robots cosmetic
    • Tool “find_home_robots” changed its title: Robots pour la maison → Robots for the home cosmetic
    • Tool “find_programmable_robots” changed its title: Robots programmables → Programmable robots cosmetic
    • Tool “find_robots_by_capability” changed its title: Robots par capacité démontrée → Robots by demonstrated capability cosmetic
    • Tool “find_robots_by_utility” changed its title: Robots par utilité → Robots by utility cosmetic
    • Tool “get_methodology” changed its title: Méthodologie Vuntum → Vuntum methodology cosmetic
    • Tool “get_recent_changes” changed its title: Changements récents → Recent changes cosmetic
    • Tool “get_robot” changed its title: Fiche robot → Robot sheet cosmetic
    • Tool “get_robot_availability” changed its title: Disponibilité d’un robot → Robot availability cosmetic
    • Tool “get_robot_claims” changed its title: Affirmations d’un robot → Robot claims cosmetic
    • Tool “get_robot_prices” changed its title: Prix d’un robot → Robot prices cosmetic
    • Tool “get_robot_sources” changed its title: Sources d’un robot → Robot sources cosmetic
    • Tool “search_open_source_projects” changed its title: Projets open source → Open source projects cosmetic
    • Tool “search_robots” changed its title: Rechercher des robots → Search robots cosmetic
    • Tool “search_site” changed its title: Rechercher sur Vuntum → Search Vuntum cosmetic
  • 4 Oct 26 +66
    • HSTS header: unverified → fail ▼ security
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • First check of Judged manipulation: pass security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Tool coverage: 70 functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: pass functional
  • 3 Oct 26 6

    First indexed and scored.

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 16 Oct 2026 · Probed https://vuntum.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=vuntum.com CN=YE1,O=Let's Encrypt,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA384 517fe2853d41b7517fd5fd7d2bf95ee86b6
SANs: vuntum.com, www.vuntum.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 secure

Validation of vuntum.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
vuntum.com. present 34861 13 Verified
vuntum.com. Verified address RRset verified with the apex keys
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=63072000; includeSubDomains
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://vuntum.com/mcp Verified 200
http (plaintext) http://vuntum.com/mcp HTTPS enforced 301 https://vuntum.com/mcp
MCP tools · 16 exposed · ~1,563 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_robots ~112

Comparison of 2 to 4 published robots on the columns of the Vuntum comparison. Each row says whether the values differ (`differs`); `differingPredicates` lists what sets the robots apart, `missingByRobot` what is not disclosed. `locale: "fr"` for French.

NameTypeReqDescription
localestring–Language of the texts and addresses: "fr" (default) or "en". The figures and the sources are identical.
slugsarrayyes–

No output schema declared.

No examples provided.

find_home_robots ~75

Robots with a validated claim that they handle household tasks. `locale: "fr"` for French.

NameTypeReqDescription
limitinteger–Maximum number of results (50 max).
localestring–Language of the texts and addresses: "fr" (default) or "en". The figures and the sources are identical.

No output schema declared.

No examples provided.

find_programmable_robots ~83

Robots with a public SDK, Python API, ROS or MCP, by deterministic criteria. `locale: "fr"` for French.

NameTypeReqDescription
limitinteger–Maximum number of results (50 max).
localestring–Language of the texts and addresses: "fr" (default) or "en". The figures and the sources are identical.

No output schema declared.

No examples provided.

find_robots_by_capability ~128

Published robots with a validated claim behind each requested capability: marcher, courir, escaliers, se-relever, saisir, plier-linge, ranger, navigation, parler. Never inferred from a category: each capability returns the claim, its source and its level of evidence. `locale: "fr"` for French.

NameTypeReqDescription
capabilitiesarrayyes–
limitinteger–Maximum number of results (50 max).
localestring–Language of the texts and addresses: "fr" (default) or "en". The figures and the sources are identical.

No output schema declared.

No examples provided.

find_robots_by_utility ~166

Published robots that have a given utility (the keys are the site's French slugs): menage, jardin, cuisine, compagnie, education, loisirs, aide-personne, medical, reeducation, recherche, logistique, livraison, accueil, nettoyage-pro, inspection, construction, agriculture, industrie, exploration, telepresence, secours, defense-securite, polyvalent, autres. A robot often has several (`utilities` field of each sheet). `locale: "en"` gives the English label and page.

NameTypeReqDescription
limitinteger–Maximum number of results (50 max).
localestring–Language of the texts and addresses: "fr" (default) or "en". The figures and the sources are identical.
utilitystringyes–

No output schema declared.

No examples provided.

get_article ~96

A published article (text, date, sources) from its URL identifier (the `slug` of an article result, in the same language). `locale: "fr"` for French.

NameTypeReqDescription
localestring–Language of the texts and addresses: "fr" (default) or "en". The figures and the sources are identical.
slugstringyesURL identifier of the robot sheet, for example "g1".

No output schema declared.

No examples provided.

get_methodology ~82

Definitions of the levels of evidence, the statuses, the freshness limits and the confidence score that come with every Vuntum value, as written on the methodology page. `locale: "fr"` for French.

NameTypeReqDescription
localestring–Language of the texts and addresses: "fr" (default) or "en". The figures and the sources are identical.

No output schema declared.

No examples provided.

get_recent_changes ~75

Public change log: publications, corrections, price changes. `locale: "fr"` for French sentences.

NameTypeReqDescription
limitinteger–Maximum number of results (50 max).
localestring–Language of the texts and addresses: "fr" (default) or "en". The figures and the sources are identical.

No output schema declared.

No examples provided.

get_robot ~90

Full sheet of a published robot: summary, form, use, utilities, characteristics, prices, availability, sources. `locale: "fr"` for French.

NameTypeReqDescription
localestring–Language of the texts and addresses: "fr" (default) or "en". The figures and the sources are identical.
slugstringyesURL identifier of the robot sheet, for example "g1".

No output schema declared.

No examples provided.

get_robot_availability ~79

Availability state by market, with observation date. `locale: "fr"` for French notes.

NameTypeReqDescription
localestring–Language of the texts and addresses: "fr" (default) or "en". The figures and the sources are identical.
slugstringyesURL identifier of the robot sheet, for example "g1".

No output schema declared.

No examples provided.

get_robot_claims ~92

All the validated claims of a robot, with evidence, source and quote. `locale: "fr"` for French values.

NameTypeReqDescription
localestring–Language of the texts and addresses: "fr" (default) or "en". The figures and the sources are identical.
predicatestring––
slugstringyesURL identifier of the robot sheet, for example "g1".

No output schema declared.

No examples provided.

get_robot_prices ~80

Observed prices by market, price type and date. `locale: "fr"` for French notes.

NameTypeReqDescription
localestring–Language of the texts and addresses: "fr" (default) or "en". The figures and the sources are identical.
slugstringyesURL identifier of the robot sheet, for example "g1".

No output schema declared.

No examples provided.

get_robot_sources ~79

Sources behind the published claims of a robot. `locale: "fr"` for French source names.

NameTypeReqDescription
localestring–Language of the texts and addresses: "fr" (default) or "en". The figures and the sources are identical.
slugstringyesURL identifier of the robot sheet, for example "g1".

No output schema declared.

No examples provided.

search_open_source_projects ~99

Open source repositories related to robotics listed by Vuntum. No English description is written for a repository: with `locale: "en"` only the repository's own words are returned.

NameTypeReqDescription
limitinteger–Maximum number of results (50 max).
localestring–Language of the texts and addresses: "fr" (default) or "en". The figures and the sources are identical.
querystring––

No output schema declared.

No examples provided.

search_robots ~117

Full-text search over the published robot sheets: accents ignored, word starts, synonyms, close spelling, ranked by relevance. `matchQuality` says whether all the words, some of them or a close spelling were found. `locale: "fr"` for French texts and addresses.

NameTypeReqDescription
limitinteger–Maximum number of results (50 max).
localestring–Language of the texts and addresses: "fr" (default) or "en". The figures and the sources are identical.
querystringyes–

No output schema declared.

No examples provided.

search_site ~110

The site search: robots, manufacturers and articles (full article text included). Can be filtered by type. Returns the type, title, summary and address of each result. `locale: "fr"` for French.

NameTypeReqDescription
limitinteger–Maximum number of results (50 max).
localestring–Language of the texts and addresses: "fr" (default) or "en". The figures and the sources are identical.
querystringyes–
typesarray––

No output schema declared.

No examples provided.

Install

How do I install the Vuntum MCP server?

Vuntum is a hosted endpoint at https://vuntum.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 · vuntum.com

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

What is the Vuntum MCP server?

Vuntum is an MCP server listed in the public MCP registry as com.vuntum/mcp. Sourced, dated data on consumer robots and physical AI: specs, prices, availability, evidence. This page covers its hosted endpoint (https://vuntum.com/mcp).

Is the Vuntum MCP server safe to use?

Vuntum scores 80 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 Vuntum MCP server expose?

Vuntum exposes 16 tools: get_methodology, search_robots, search_site, get_article, get_robot, and 11 more. Their descriptions and schemas cost roughly 1,563 tokens of context every time the server is loaded.

Does the Vuntum MCP server require authentication?

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

Is the Vuntum MCP server still maintained?

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