Skip to content

The Leos studio MCP server

studio.theleos/studiotheleos.studiostreamable-httpv1.0.0Scanned

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

7 tools: 1 do something that can't be undone, 4 change things and 2 only read.

Tools: 0 delete, 1 irreversible, 4 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the The Leos studio MCP server can do

The The Leos studio MCP server is published by theleos.studio, a domain the MCP Registry verified. It has 7 tools. It can do things that cannot be undone, such as sending, paying or publishing (submit_brief) and create or change data (4 tools: talk_to_the_studio, estimate_budget, check_availability and request_call), but cannot delete data. 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Can't be undone 1Claude Code: ask
  • submit_briefSend a project brief to the studio on behalf of a client.No findings

    Why it is in this group

    • The name "submit_brief" says "submit": a word for a change.
    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
    Description, as the server wrote it
    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.
Changes things 4Claude Code: ask
  • check_availabilityEvery 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 gro…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • estimate_budgetStarting prices from the rate card (EUR, plus IVA, photo and video included).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Starting prices from the rate card (EUR, plus IVA, photo and video included). Final quotes are confirmed by a person.
  • request_callBook a 30-minute call with the studio at one of the slots from check_availability.No findings

    Why it is in this group

    • The name "request_call" says "request": a word for a change.
    Description, as the server wrote it
    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.
  • talk_to_the_studioTalk 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), an…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 2Show 2 read-only tools
  • list_servicesWhat The Leos (film, photography and design studio, Milan and New York) makes, who for, and its rentable daylight studio in Milan.No findings

    Why it is in this group

    • The name "list_services" says "list": a word for reading.
    Description, as the server wrote it
    What The Leos (film, photography and design studio, Milan and New York) makes, who for, and its rentable daylight studio in Milan.
  • list_workThe studio's published projects, optionally filtered by kind (brands, events, businesses) or a word (e.g.No findings

    Why it is in this group

    • The name "list_work" says "list": a word for reading.
    Description, as the server wrote it
    The studio's published projects, optionally filtered by kind (brands, events, businesses) or a word (e.g. 'eyewear', 'jewellery', 'fashion week').

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:22 UTC, unchanged since Nov 7, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (1 irreversible, 4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.theleos.studio/mcp: tools/list returned 7 tools to an anonymous client, including submit_brief (irreversible), talk_to_the_studio (write), estimate_budget (write), check_availability (write), request_call (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools3 changed.~3 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http studio https://www.theleos.studio/mcp
claude mcp add --transport http studio https://www.theleos.studio/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__studio__list_services",
      "mcp__studio__list_work"
    ],
    "ask": [
      "mcp__studio__talk_to_the_studio",
      "mcp__studio__estimate_budget",
      "mcp__studio__check_availability",
      "mcp__studio__submit_brief",
      "mcp__studio__request_call"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as studio. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/studio.theleos/studio/verify?hash=9d1df6eccb3e2729fcc391dbe1f4d6086f17e9c7d318802993b35e99c66cd096" | jq -e '.changed == false'

Pinned hash 9d1df6eccb3e, from Nov 20, 2026, 09:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/studio.theleos/studio/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for studio.theleos/studio
[![Anlyon Radar](https://radar.anlyon.com/badge/studio.theleos/studio.svg)](https://radar.anlyon.com/servers/studio.theleos/studio)

Source: MCP Registry. Synced Nov 6, 2026, 08:18 UTC.

The Leos studio MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the The Leos studio MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the The Leos studio MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the The Leos studio MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: submit_brief.

What tools does the The Leos studio MCP server have?

7 tools: 1 irreversible, 4 write, 2 read. submit_brief, talk_to_the_studio, estimate_budget, check_availability, request_call, list_services and list_work.

Does the The Leos studio MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the The Leos studio MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the The Leos studio MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.