Home / MCP registry index / com.coworkingview/mcp
CoworkingView
com.coworkingview/mcp in the official MCP registry.
Endpoint https://mcp.coworkingview.com/mcp.
The registry describes it as: Coworking, private offices and day passes with published prices: Berlin, Madrid, London + 60 cities
We read its 10 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
list_coworking_locations resolve_coworking_query get_coworking_filter_options search_coworking_spaces get_coworking_space compare_coworking_spaces get_coworking_market_rates get_coworking_operator get_coworking_place_guide get_coworking_public_holidays
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-coworkingview-mcp)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.