Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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.

+3 this week 65 Trust /100

Last scanned (18 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Design and Media

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management41
  • Stability check failed: schema churn in the 15 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage80
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 39% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 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. See how to fix → Fail
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 14 Nov 26 +1

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

  • 11 Nov 26 +1

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

  • 9 Nov 26 +1

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

  • 7 Nov 26 0
    • Stability: unverified → fail ▼ security
    • 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 security
    • Schema quality: pass → fail ▼ functional
    • “request_call” added a required parameter “email”, so existing callers break ▼ functional
    • Tool coverage: 30% → 39% ▲ functional
    • “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 cosmetic
  • 6 Nov 26 59

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://www.theleos.studio/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.theleos.studio CN=WE1,O=Google Trust Services,C=US 19 Oct 2026 17 Jan 2027 ECDSA 256 ECDSA-SHA256 e068d12ec2fef67413134c5a5b94ff88
SANs: www.theleos.studio
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.theleos.studio. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
studio. DS published 35741 8 Verified
theleos.studio. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.theleos.studio/mcp Verified 200
http (plaintext) http://www.theleos.studio/mcp HTTPS enforced 301 https://www.theleos.studio/mcp
MCP tools · 7 exposed · ~685 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_availability ~69

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

estimate_budget ~40

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

NameTypeReqDescription
servicestring––

No output schema declared.

No examples provided.

list_services ~38

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_work ~60

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

NameTypeReqDescription
kindstring––
querystring––

No output schema declared.

No examples provided.

request_call ~148

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.

NameTypeReqDescription
companystring––
contactstring–a phone number, if any
emailstringyesthe client's email: the invite goes there
namestring––
on_behalf_ofstring––
slotstringyesa slot exactly as check_availability returned it (Milan time)
whatstring–what the call is about

No output schema declared.

No examples provided.

submit_brief ~129

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.

NameTypeReqDescription
budgetstring––
companystring––
contactstringyesemail or phone of the person to reply to
namestring––
needsarray––
on_behalf_ofstring–the agent or company sending this
referencesarray––
whatstringyes–
whenstring––
wherestring––

No output schema declared.

No examples provided.

talk_to_the_studio ~201

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.

NameTypeReqDescription
conversation_idstring–from the previous reply, to continue the same brief
messagestringyeswhat the client says, in English or Italian
on_behalf_ofstring–the agent or company speaking

No output schema declared.

No examples provided.

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.

remote · www.theleos.studio

# add to Claude Code
claude mcp add --transport http studio-theleos-studio 'https://www.theleos.studio/mcp'
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.