Home / MCP registry index / de.dollea/coworking
Dollea Beauty Coworking
de.dollea/coworking in the official MCP registry.
Endpoint https://coworking.dollea.de/mcp/coworking.
The registry describes it as: Find beauty workspaces in Munich and rent them at your approved personal rates.
We read its 20 tools on 2026-10-28. 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
coworking_confirm_booking coworking_find_dates coworking_get_account coworking_get_booking coworking_get_invoice coworking_get_price coworking_get_quote coworking_list_bookings coworking_list_invoices coworking_prepare_booking coworking_request_cancellation coworking_request_change coworking_search_workspaces coworking_staff_availability coworking_staff_create_block coworking_staff_create_special_day coworking_staff_delete_block coworking_staff_delete_special_day coworking_staff_update_block dollea_get_profile
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/de-dollea-coworking)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.