Home / MCP registry index / com.vuntum/mcp
Vuntum
com.vuntum/mcp in the official MCP registry.
Endpoint https://vuntum.com/mcp. Source: github.com/RAAAAAGEEEEE/vuntum-mcp.
The registry describes it as: Sourced, dated data on consumer robots and physical AI: specs, prices, availability, evidence.
We read its 16 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
get_methodology search_robots search_site get_article get_robot get_robot_claims get_robot_sources get_robot_prices get_robot_availability compare_robots find_home_robots find_robots_by_utility find_robots_by_capability find_programmable_robots get_recent_changes search_open_source_projects
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-vuntum-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.