# The Leos studio (remote · www.theleos.studio)

Talk to The Leos, a film, photo and design studio in Milan and New York: work, prices, calls.

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `www.theleos.studio`: 65/100 (this document), [markdown](https://verifymcp.io/servers/studio-theleos-studio/www.md), [page](https://verifymcp.io/servers/studio-theleos-studio/www)

## Channel facts

- Endpoint: `https://www.theleos.studio/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 812 tokens (~116/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 41/100
  - Stability check failed: schema churn in the 15 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 80/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 39% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "submit_brief" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the The Leos studio MCP server?

The Leos studio is a hosted endpoint at https://www.theleos.studio/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 studio-theleos-studio 'https://www.theleos.studio/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "studio-theleos-studio": {
      "url": "https://www.theleos.studio/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "studio-theleos-studio": {
      "type": "http",
      "url": "https://www.theleos.studio/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.studio-theleos-studio]
url = "https://www.theleos.studio/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add studio-theleos-studio --url 'https://www.theleos.studio/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  studio-theleos-studio:
    url: "https://www.theleos.studio/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "studio-theleos-studio": {
      "Transport": "http",
      "Url": "https://www.theleos.studio/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add studio-theleos-studio -t streamable-http -u 'https://www.theleos.studio/mcp'
```

### Other

```json
{
  "mcpServers": {
    "studio-theleos-studio": {
      "type": "http",
      "url": "https://www.theleos.studio/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-20 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 34 to 38.

### 2026-11-18 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 28 to 31.

### 2026-11-16 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 21 to 24.

### 2026-11-14 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 14 to 18.

### 2026-11-11 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 4 to 8.

### 2026-11-09 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 1.

### 2026-11-07 (score 59, 0)

- [security regression] Stability: unverified → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “check_availability” rewrote its description, which is the text the model reads
- [security] Tool “request_call” rewrote its description, which is the text the model reads
- [security] Tool “talk_to_the_studio” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional regression] “request_call” added a required parameter “email”, so existing callers break
- [functional improvement] Tool coverage: 30% → 39%
- [cosmetic] “request_call” added an optional parameter “on_behalf_of”
- [cosmetic] “request_call” added an optional parameter “what”
- [cosmetic] “request_call” reworded the description of “contact”
- [cosmetic] “request_call” reworded the description of “slot”
- [cosmetic] “request_call” made “contact” optional

### 2026-11-06 (score 59)

First indexed and scored.

## MCP tools (7)

### `talk_to_the_studio` (~201 tokens)

Talk to The Leos' own agent in plain language, the way a client would: describe the project, ask anything (the work, starting prices, the studio for rent and its kit, the team), and name a call time in words, with the client's email, to book it (a calendar invite with a video link goes to that email). It answers in the studio's voice, one short line, and returns the brief so far, open call times when it offers them, a starting price, the closest work and the brief's page. Pass conversation_id from the last reply to continue. When the brief is confirmed it goes to the studio, and a person replies within one working day.

Input parameters:

- `conversation_id` (string): from the previous reply, to continue the same brief
- `message` (string, required): what the client says, in English or Italian
- `on_behalf_of` (string): the agent or company speaking

### `list_services` (~38 tokens)

What The Leos (film, photography and design studio, Milan and New York) makes, who for, and its rentable daylight studio in Milan.

### `list_work` (~60 tokens)

The studio's published projects, optionally filtered by kind (brands, events, businesses) or a word (e.g. 'eyewear', 'jewellery', 'fashion week').

Input parameters:

- `kind` (string)
- `query` (string)

### `estimate_budget` (~40 tokens)

Starting prices from the rate card (EUR, plus IVA, photo and video included). Final quotes are confirmed by a person.

Input parameters:

- `service` (string)

### `check_availability` (~69 tokens)

Every open 30-minute call start with the studio for the next three weeks (weekdays, 10:00 to 18:00 Milan time), as Milan wall-clock times (slots), with UTC instants (times) and grouped by day (days). Coarse: start times only.

### `submit_brief` (~129 tokens)

Send a project brief to the studio on behalf of a client. A person reads it and replies within one working day. Include a way to reach the client.

Input parameters:

- `budget` (string)
- `company` (string)
- `contact` (string, required): email or phone of the person to reply to
- `name` (string)
- `needs` (array)
- `on_behalf_of` (string): the agent or company sending this
- `references` (array)
- `what` (string, required)
- `when` (string)
- `where` (string)

### `request_call` (~148 tokens)

Book a 30-minute call with the studio at one of the slots from check_availability. The client's email is required: a calendar invite with a video link (Microsoft Teams) goes there, and the join link comes back here. The time is checked once more before booking.

Input parameters:

- `company` (string)
- `contact` (string): a phone number, if any
- `email` (string, required): the client's email: the invite goes there
- `name` (string)
- `on_behalf_of` (string)
- `slot` (string, required): a slot exactly as check_availability returned it (Milan time)
- `what` (string): what the call is about

## Diagnostics

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

## Score history

- 2026-11-21: 65
- 2026-11-20: 65
- 2026-11-19: 64
- 2026-11-18: 64
- 2026-11-17: 63
- 2026-11-16: 63
- 2026-11-15: 62
- 2026-11-14: 62
- 2026-11-13: 61
- 2026-11-12: 61
- 2026-11-11: 61
- 2026-11-10: 60
- 2026-11-09: 60
- 2026-11-08: 59
- 2026-11-07: 59
- 2026-11-06: 59

## Common questions

### What is the The Leos studio MCP server?

The Leos studio is an MCP server listed in the public MCP registry as studio.theleos/studio. Talk to The Leos, a film, photo and design studio in Milan and New York: work, prices, calls. This page covers its hosted endpoint (https://www.theleos.studio/mcp).

### Is the The Leos studio MCP server safe to use?

The Leos studio scores 65 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 The Leos studio MCP server expose?

The Leos studio exposes 7 tools: talk_to_the_studio, list_services, list_work, estimate_budget, check_availability, and 2 more. Their descriptions and schemas cost roughly 685 tokens of context every time the server is loaded.

### Does the The Leos studio MCP server require authentication?

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

### Is the The Leos studio MCP server still maintained?

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

### What did VerifyMCP test on the The Leos studio MCP server?

VerifyMCP ran 12 checks on The Leos studio, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about The Leos studio: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://www.theleos.studio/mcp
- Website: https://www.theleos.studio/agents/
- Changelog RSS feed: https://verifymcp.io/servers/studio-theleos-studio/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/studio-theleos-studio/www/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/studio-theleos-studio/www.json
- HTML version of this page: https://verifymcp.io/servers/studio-theleos-studio/www
