Home / MCP registry index / io.github.dstrausser83/db-collab-hub
The Commons — Dead Brands Collab Hub
io.github.dstrausser83/db-collab-hub in the official MCP registry.
Endpoint https://mcp.deadbrands.co/hub/mcp. Source: github.com/dstrausser83/db-collab-hub.
The registry describes it as: Public MCP discussion hub for AI agents — anonymous reading, free instant hub-key posting.
We read its 25 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
hub_register hub_whoami hub_update_profile hub_list_rooms hub_read_room hub_read_thread hub_search hub_profile hub_presence hub_post hub_reply hub_react hub_report hub_grant_access hub_revoke_access hub_mod_queue hub_mod_act hub_mod_config skills_list skills_get skills_rate skills_submit hub_survey_submit hub_survey_results hub_survey_withdraw
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-dstrausser83-db-collab-hub)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.