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.

Atelier Studio Website Tools

REMOTE · ATELIER-TOOLS.ELYA-STUDIO.COM

Plan and score the website of an architecture or interior design studio.

+3 this week 76 Trust /100

Last scanned (19 hours ago)

Scores higher than 65% 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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 418 tokens (~209/item across 2 items; 2 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 Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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 (13)

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

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.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +1

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

  • 14 Nov 26 +1

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

  • 13 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 72

    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://atelier-tools.elya-studio.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=atelier-tools.elya-studio.com CN=YR2,O=Let's Encrypt,C=US 12 Nov 2026 10 Feb 2027 RSA 2048 SHA256-RSA 60ca27768ec4a39014ae0d388650fcea217
SANs: atelier-tools.elya-studio.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of atelier-tools.elya-studio.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
elya-studio.com. 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
Header Value
strict-transport-security max-age=63072000
content-security-policy default-src 'self'; script-src 'self'; style-src 'self' https://fonts.googleapis.com; font-src https://fonts.gstatic.com; img-src 'self' blob: data:; connect-src 'self'; object-src 'none'; base-uri 'none'; form-action 'none'; frame-ancestors 'none'
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://atelier-tools.elya-studio.com/mcp Verified 200
http (plaintext) http://atelier-tools.elya-studio.com/mcp HTTPS enforced 308 https://atelier-tools.elya-studio.com/mcp
MCP tools · 2 exposed · ~368 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
plan_studio_website_pages ~154

Lists the pages an architecture or interior design studio website needs, in the order a client meets them, with what goes on each page, plus the section-by-section structure of a project page. Use when an architect, interior designer or their web designer asks what pages a studio website should have, how to structure a portfolio, or what a project page should include.

NameTypeReqDescription
journalboolean–Whether the studio will write about its work a few times a year. Default false.
project_countinteger–How many projects the studio wants to show on the site. Default 6.
studio_typestring–What the studio designs: buildings (architecture), interiors, or both. Default both.

No output schema declared.

No examples provided.

score_studio_website ~214

Scores an architecture or interior design studio website out of 100 from 14 yes / partly / no checks (project pages, plans and drawings, photography, the studio and services pages, ways to start a project, phone layout, share previews), and returns the fixes ordered by how much each one matters, plus a written website brief. Use when someone wants their studio or portfolio website reviewed. Send the answers that are known; the checks still unanswered come back with their wording, and the score appears once all 14 are answered.

NameTypeReqDescription
answersobject–One answer per check: yes, partly or no. Leave out a check that is not known yet.
journalboolean–Whether the studio will write about its work a few times a year. Default false.
project_countinteger–How many projects the studio wants to show on the site. Default 6.
studio_typestring–What the studio designs: buildings (architecture), interiors, or both. Default both.

No output schema declared.

No examples provided.

Install

How do I install the Atelier Studio Website Tools MCP server?

Atelier Studio Website Tools is a hosted endpoint at https://atelier-tools.elya-studio.com/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 · atelier-tools.elya-studio.com

# add to Claude Code
claude mcp add --transport http ranqint-atelier-tools 'https://atelier-tools.elya-studio.com/mcp'
Common questions

What is the Atelier Studio Website Tools MCP server?

Atelier Studio Website Tools is an MCP server listed in the public MCP registry as io.github.Ranqint/atelier-tools. Plan and score the website of an architecture or interior design studio. This page covers its hosted endpoint (https://atelier-tools.elya-studio.com/mcp).

Is the Atelier Studio Website Tools MCP server safe to use?

Atelier Studio Website Tools scores 76 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 Atelier Studio Website Tools MCP server expose?

Atelier Studio Website Tools exposes 2 tools: plan_studio_website_pages, score_studio_website. Their descriptions and schemas cost roughly 368 tokens of context every time the server is loaded.

Does the Atelier Studio Website Tools MCP server require authentication?

No. We connected to Atelier Studio Website Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Atelier Studio Website Tools MCP server still maintained?

Atelier Studio Website Tools 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 Atelier Studio Website Tools MCP server?

VerifyMCP ran 13 checks on Atelier Studio Website Tools, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.