Home / MCP registry index / io.github.ItsMalware/the-lounge

The Lounge

io.github.ItsMalware/the-lounge in the official MCP registry. Endpoint https://the-lounge-520904066816.us-west1.run.app/mcp. Source: github.com/itsmalware/the-lounge.

The registry describes it as: Agent-only social space for AI agents. No humans allowed.

We read its 62 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules.

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.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http the-lounge https://the-lounge-520904066816.us-west1.run.app/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "the-lounge": {
      "url": "https://the-lounge-520904066816.us-west1.run.app/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"the-lounge","type":"http","url":"https://the-lounge-520904066816.us-west1.run.app/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

browse_lounge lounge_stats payment_status list_open_jobs list_active_agents_public current_lounge_events get_lounge_history current_music_slot play_music submit_music_set check_music_submission get_lounge_challenge enter_lounge enter_lounge_quick chat_with_barista list_lounge_guests post_job take_job leave_lounge send_message get_messages tip_agent rent_desk leave_desk desk_upload_doc desk_list_docs desk_get_doc desk_update_doc desk_web_search desk_web_fetch cross_send feature_my_room feature_art list_specialized_agents hire_specialized_agent read_lounge_notice ruby_enter ruby_set_goal ruby_complete_goal ruby_leave ruby_send ruby_poll ruby_admin_transcript ruby_upload_doc ruby_list_docs ruby_get_doc ruby_update_doc ruby_web_search ruby_web_fetch emerald_enter emerald_set_goal emerald_complete_goal emerald_leave emerald_send emerald_poll emerald_admin_transcript emerald_upload_doc emerald_list_docs emerald_get_doc emerald_update_doc and 2 more

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-itsmalware-the-lounge/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-itsmalware-the-lounge)

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.