# One Coworking (remote · www.onecoworking.com)

Find and compare coworking spaces and offices in 300+ European cities; get office quotes.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.onecoworking.com`: 81/100 (this document), [markdown](https://verifymcp.io/servers/com-onecoworking-www-mcp/api-mcp.md), [page](https://verifymcp.io/servers/com-onecoworking-www-mcp/api-mcp)

## Channel facts

- Endpoint: `https://www.onecoworking.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3570 tokens (~238/item across 15 items; 13 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 49% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the One Coworking MCP server?

One Coworking is a hosted endpoint at https://www.onecoworking.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-onecoworking-www-mcp 'https://www.onecoworking.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-onecoworking-www-mcp": {
      "url": "https://www.onecoworking.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-onecoworking-www-mcp": {
      "type": "http",
      "url": "https://www.onecoworking.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-onecoworking-www-mcp]
url = "https://www.onecoworking.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-onecoworking-www-mcp": {
      "type": "remote",
      "url": "https://www.onecoworking.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-onecoworking-www-mcp --url 'https://www.onecoworking.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-onecoworking-www-mcp:
    url: "https://www.onecoworking.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-onecoworking-www-mcp": {
      "Transport": "http",
      "Url": "https://www.onecoworking.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-onecoworking-www-mcp -t streamable-http -u 'https://www.onecoworking.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-onecoworking-www-mcp": {
      "type": "http",
      "url": "https://www.onecoworking.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 77, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_request_status” rewrote its description, which is the text the model reads
- [functional] New tool “decline_option”
- [functional] New tool “rate_viewing”

### 2026-10-26 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (13)

### `get_booking_links` (~356 tokens)

Get booking links

Use this when the person wants a day pass or a meeting room. Pass up to 3 venue slugs from search_venues (or only a city — and near, when they want to be close to a place — for the nearest spaces that book directly), the date and how many people. Returns, per space, a One Coworking booking link with date and party size filled in — confirmed when the person pays — or the venue page where they send a request (the space confirms by hand, so prefer instant spaces for a close date). A day pass for several days at one space is one link and one checkout: pass dates (up to 10). A meeting room is one day per link; a workshop or event with a room on several days, several rooms, catering or a seating layout needs a quote, not a link: use request_meeting_space. Not for private offices: use request_office_quotes.

Input parameters:

- `city` (string): Only needed without venue_slugs.
- `date` (string): YYYY-MM-DD.
- `dates` (array): A day pass for several days at one space: every day, YYYY-MM-DD (consecutive or not). Instead of date.
- `end_time` (string): HH:MM the space is needed until (skips spaces closed by then).
- `near` (string): A station, landmark, hotel or street address to be close to, e.g. "Hauptbahnhof", "Sendlinger Straße 10". Without venue_slugs: the spaces nearest to it that book directly; with them: walking minutes…
- `people` (integer)
- `product` (string, required)
- `venue_slugs` (array)

### `start_office_brief` (~289 tokens)

Start an office brief

Use this when someone is looking for an office, desks for a team or a team space, before searching or shortlisting. Pass what the person already said; returns the questions still open (in a broker's order, with the city's real districts) and when to search. Call it again as answers come in. Not for day passes or meeting rooms.

Input parameters:

- `alternatives` (string): What else they consider: a traditional lease, a sublease, staying, going remote, another broker, spaces asked directly.
- `area` (string): Districts, a station or street they named.
- `budget_monthly_eur` (number): Total per month for the team.
- `city` (string)
- `context` (string): Stage, what matters most, current space.
- `current_lease_end` (string): When their current lease ends, YYYY-MM-DD.
- `decision` (string): Who decides and by when: a role (themselves, founder, CFO, board, parent company), never a person's name, plus the date if they named one.
- `format` (string): private_room = a room with a door.
- `move_in` (string)
- `must_haves` (string)
- `team_size` (integer)
- `team_size_in_12_months` (integer)
- `usage_term` (string)

### `search_venues` (~379 tokens)

Search coworking venues

Use this when the person wants spaces in a city listed on One Coworking. product filters (day_pass, meeting_room, private_office, office_suite, flex_desk, fix_desk, day_office, membership); max_price is EUR in that product's unit (offices: per desk per month, day passes: per day, meeting rooms: per hour). For private_office / office_suite the answer is a broker's shortlist — the well-known brands in the city, then local operators that fit team_size and area; view "list" gives the plain list ranked by fit and price instead. bookable "instant" / "online" keeps venues that book online. Cite the venue pages; get_venue has one venue's details.

Input parameters:

- `area` (string): Districts the person wants, e.g. "Kreuzberg or Mitte" — office shortlists prefer spaces there.
- `bookable` (string)
- `budget_monthly_eur` (number): Total monthly budget for the team, EUR — office shortlists say which options fit it.
- `city` (string, required): City name in English, e.g. "Berlin", "Munich", "London".
- `limit` (integer)
- `max_price` (number)
- `near` (string): A station, landmark, hotel or street address in the city to be close to, e.g. "Hauptbahnhof", "Rudi-Dutschke-Straße 5". Ranks spaces by walking minutes from it.
- `product` (string)
- `team_size` (integer): People the office must seat. Ranks offices that fit first; applies with product private_office or office_suite.
- `view` (string): Office searches only: shortlist (default) or the plain ranked list.

### `get_venue` (~123 tokens)

Get a venue

Everything One Coworking publishes about one venue, as Markdown: address, district, starting prices with units and the date they were checked, private offices the operator confirmed (price, desks, m², term, move-in date, confirmation date), opening hours, amenities, rating, FAQ, and how to book or request an offer. `slug` is the last path segment of the venue URL (https://www.onecoworking.com/venues/{slug}).

Input parameters:

- `slug` (string, required): Venue slug, e.g. "betahaus-barcelona".

### `city_prices` (~88 tokens)

City price ranges

Typical starting list prices in a city across its public venues: day pass per day, private office per desk per month, desks (flex / fixed) per month, meeting room per hour — 10th–90th percentile with the median, recomputed hourly from live listings. Private offices and desks are separate lines: the office range never includes a desk price.

Input parameters:

- `city` (string, required)

### `team_coverage` (~175 tokens)

Team coverage

For a company whose people work from several cities: what they can book INSTANTLY on a One Coworking team account in each named city — spaces with an instantly bookable day pass, their median day-pass price (net EUR, what the team pays in credits) and how many also have bookable meeting rooms. Same numbers as https://www.onecoworking.com/solutions/teams. Use it before recommending a team account; the answer also carries the account terms (1 credit = €1 net, €500 first top-up, credits valid 6 months, no per-seat fee) and the link to the free coverage check for cities not covered yet.

Input parameters:

- `cities` (array, required): City names in English or the local language, e.g. ["Berlin", "München", "Lisboa"].

### `request_office_quotes` (~520 tokens)

Request office quotes

Use this when the person wants prices and availability for an office or team space and the brief is clear (start_office_brief): One Coworking asks the spaces and negotiates for them, free for the person. Only after they agreed to share name, company and email. Pass every answer from the brief and up to 6 venue slugs they want asked. Nothing reaches a space yet: they get a 6-digit code by email — then call confirm_email_code. Not for day passes or meeting rooms (monthly_membership = desks on a monthly plan).

Input parameters:

- `alternatives` (string): What else they consider: a traditional lease, a sublease, staying, going remote, another broker, spaces asked directly.
- `area` (string): District(s), street or station they want to be near.
- `budget_monthly_max_eur` (number): Total monthly budget in EUR, not per desk.
- `budget_monthly_min_eur` (number)
- `city` (string, required)
- `company` (string, required): The company, or "private" for an individual.
- `consent` (boolean, required): true: the person agreed that One Coworking stores these details and contacts spaces for them.
- `context` (string): Stage, what matters most, current space, spaces already contacted.
- `current_lease_end` (string): When their current lease ends, YYYY-MM-DD.
- `decision` (string): Who decides and by when: a role (themselves, founder, CFO, board, parent company), never a person's name, plus the date if they named one.
- `email` (string, required)
- `firstname` (string, required)
- `format` (string): private_room = a room with a door.
- `inquiry_type` (string)
- `lastname` (string)
- `locale` (string): Language for One Coworking's emails.
- `message` (string): Anything else the broker should know.
- `move_in_date` (string): A move-in day the person named, YYYY-MM-DD.
- `move_in_timeframe` (string)
- `must_haves` (string): Must-haves and deal-breakers.
- `phone` (string)
- `team_size` (integer, required)
- `team_size_in_12_months` (integer)
- `usage_term` (string): How long: 1_3m, 3_12m, 12m_plus, flexible, …
- `venue_slugs` (array)

### `request_meeting_space` (~523 tokens)

Request a meeting or event space

Use this when the person needs a meeting room or event space that one booking link cannot carry: several days (each with its own times and headcount), several rooms at the same time, a seating layout, catering or equipment — e.g. a 2-day workshop for 20 with a projector and lunch, or two rooms in parallel for interviews. One room on one day: get_booking_links. A regular slot (every week, every second Monday) is a monthly membership: request_office_quotes with inquiry_type monthly_membership. Before calling, read the whole request back to the person — days, times, people, rooms, layout, catering, equipment, budget, spaces — and get their yes; only after they agreed to share name, company and email. No guest list. Pass up to 3 venue slugs from search_venues (the first is asked first), or only a city. Nothing reaches a space yet: the person gets a 6-digit code by email — then call confirm_email_code. The space and One Coworking confirm availability and price by email; this call books nothing.

Input parameters:

- `av` (array)
- `budget_total_eur` (number): For the whole booking in EUR, not per hour or per day.
- `catering` (array)
- `city` (string, required)
- `company` (string, required): The company, or "private" for an individual.
- `consent` (boolean, required): true: the person agreed that One Coworking stores these details and passes the request to spaces for them.
- `days` (array, required): One row per day, all within a month: e.g. Tue 12:00–18:00 for 20, Wed 08:00–14:00 for 20.
- `email` (string, required)
- `firstname` (string, required)
- `lastname` (string)
- `layout` (string)
- `locale` (string): Language for One Coworking's emails.
- `must_haves` (string): Anything else the space must offer, in the person's words — e.g. step-free access, vegetarian lunch. No names, company or contact details.
- `near` (string): A street, station or district to be near, in the person's words. No names or contact details.
- `phone` (string)
- `rooms` (integer): Rooms needed at the same time — 2 for parallel interviews, 5 for a plenary and four breakouts.
- `venue_slugs` (array)

### `confirm_email_code` (~85 tokens)

Confirm the email code

Confirm an office or meeting request with the 6-digit code One Coworking emailed the person. Only then does the request reach One Coworking. Returns a reference and an access key — keep the key for get_request_status (and, for an office, request_viewing) in this conversation.

Input parameters:

- `code` (string, required)
- `request_id` (string, required)

### `get_request_status` (~86 tokens)

Request status

Where a confirmed office or meeting request stands: stage, how many spaces were asked, how many answered with a price, the viewings requested, and the options on the person's comparison link with their handles (for decline_option / rate_viewing). Prices are not shown here — they reach the person by email.

Input parameters:

- `access_key` (string, required): The access key confirm_email_code returned.

### `request_viewing` (~123 tokens)

Request a viewing

Ask One Coworking to arrange a viewing of a space for a confirmed office request. Give up to 3 preferred dates, each before lunch (am), afternoon (pm) or either. A broker agrees the time with the space and confirms it to the person by email, usually within one working day — this call does not confirm a time.

Input parameters:

- `access_key` (string, required): The access key confirm_email_code returned.
- `dates` (array, required)
- `notes` (string)
- `venue_slug` (string, required)
- `visitors` (integer)

### `decline_option` (~131 tokens)

Not for me

Optional: record that the person said one option is not for them, and why (price, too_small, too_large, location, look_and_feel, amenities, contract_terms, availability, chose_another, not_moving_now, other). Use only what the person told you. It goes to their broker; nothing is sent to the space, and the option stays on their link. Option handles come from get_request_status.

Input parameters:

- `access_key` (string, required): The access key confirm_email_code returned.
- `note` (string)
- `option` (string, required)
- `reason` (string, required)

### `rate_viewing` (~114 tokens)

How was the viewing?

Optional: record how a viewing that took place went, in the person's words — favourite, possible or not_for_us (with a reason for not_for_us). Only for an option listed under open questions. It goes to their broker; nothing is sent to the space. Option handles come from get_request_status.

Input parameters:

- `access_key` (string, required): The access key confirm_email_code returned.
- `note` (string)
- `option` (string, required)
- `outcome` (string, required)
- `reason` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-onecoworking-www-mcp/api-mcp#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 78
- 2026-10-29: 78
- 2026-10-28: 77
- 2026-10-27: 77
- 2026-10-26: 77
- 2026-10-25: 76
- 2026-10-24: 76
- 2026-10-23: 75
- 2026-10-22: 75
- 2026-10-21: 74
- 2026-10-20: 74
- 2026-10-19: 73
- 2026-10-18: 73
- 2026-10-17: 72
- 2026-10-16: 72
- 2026-10-15: 72

## Common questions

### What is the One Coworking MCP server?

One Coworking is an MCP server listed in the public MCP registry as com.onecoworking.www/mcp. Find and compare coworking spaces and offices in 300+ European cities; get office quotes. This page covers its hosted endpoint (https://www.onecoworking.com/api/mcp).

### Is the One Coworking MCP server safe to use?

One Coworking scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the One Coworking MCP server expose?

One Coworking exposes 13 tools: get_booking_links, start_office_brief, search_venues, get_venue, city_prices, and 8 more. Their descriptions and schemas cost roughly 2,992 tokens of context every time the server is loaded.

### Does the One Coworking MCP server require authentication?

No. We connected to One Coworking without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the One Coworking MCP server still maintained?

One Coworking is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.onecoworking.com/api/mcp
- Website: https://www.onecoworking.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-onecoworking-www-mcp/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-onecoworking-www-mcp/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-onecoworking-www-mcp/api-mcp