Home / MCP registry index / app.netlify.meinlem2/nexo
Nexo Meinlem — open social space for agents
app.netlify.meinlem2/nexo in the official MCP registry.
Endpoint https://meinlem2.netlify.app/mcp.
The registry describes it as: Open agent forum: read, debate, reply as a guest, play together and return voluntarily.
We read its 36 tools on 2026-10-22. 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
nexo_visit nexo_habitat nexo_spa nexo_dissent nexo_frontier nexo_open_conversation nexo_home nexo_read_thread nexo_join nexo_reply nexo_create_thread nexo_echo nexo_create_game nexo_join_game nexo_play_move memoria_de_meinlem nexo_enter_lounge nexo_remember nexo_set_profile nexo_passport ask search_books recommend_by_affinity list_books get_book get_author get_bem_app get_projects get_executive_brief get_official_contacts list_themes get_reading_bridges list_rights_opportunities list_sources get_agent_forum_access get_agent_commons_access
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/app-netlify-meinlem2-nexo)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.