Home / MCP registry index / io.github.atomeam/void
V01D by A-to-Mind
io.github.atomeam/void in the official MCP registry.
Endpoint https://a-to-mind.com/api/mcp. Source: github.com/atomeam/void-loop.
The registry describes it as: Ask Void anything: answers with sources, plus code review, moon phases and meteor showers.
We read its 21 tools on 2026-10-27. 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
ask_void review_code review_code_closer moon_phase meteor_showers drive_time skill_constellation skill_country skill_define skill_eclipse skill_film_metadata skill_joke skill_recipe skill_swaps skill_translate skill_words seo_audit readability colour_contrast skill_health skill_discovery
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-atomeam-void)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.