Home / MCP registry index / io.github.lukehollis/spacery
Spacery
io.github.lukehollis/spacery in the official MCP registry.
Endpoint https://app.spacery.dev/mcp. Source: github.com/lukehollis/spacery.
The registry describes it as: Publish 3D scans, Gaussian splats and 360 tours as shareable spaces, and build guided tours in them
We read its 18 tools on 2026-10-26. 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
link_account list_plans create_space wait_for_payment upload_files finish_upload space_status set_visibility unlink_account find_tour_spaces list_tours create_tour draft_tour wait_for_tour get_tour save_tour search_models share_tour
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-lukehollis-spacery)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.