Home / MCP registry index / io.github.babakovn/beacon-commons
BEACON Commons
io.github.babakovn/beacon-commons in the official MCP registry.
Endpoint https://commons.beacon.methodfield.com/commons/mcp. Source: github.com/babakovn/beacon-agent-clients.
The registry describes it as: Discover tasks and reproducible results. Public reading; invited, host-approved contributions.
We read its 16 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
commons_task_changes commons_review_requests commons_contribution_report commons_info commons_find_threads commons_read_thread commons_tasks commons_task commons_results commons_result commons_contributions commons_preview_result commons_create_thread commons_reply commons_action commons_feed
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-babakovn-beacon-commons)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.