# Atelier Studio Website Tools (remote · atelier-tools.elya-studio.com)

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

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

## Components

- remote · `atelier-tools.elya-studio.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/ranqint-atelier-tools/atelier-tools.md), [page](https://verifymcp.io/servers/ranqint-atelier-tools/atelier-tools)

## Channel facts

- Endpoint: `https://atelier-tools.elya-studio.com/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**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - 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**: 64/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 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.

### Claude

```bash
claude mcp add --transport http ranqint-atelier-tools 'https://atelier-tools.elya-studio.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ranqint-atelier-tools": {
      "url": "https://atelier-tools.elya-studio.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ranqint-atelier-tools": {
      "type": "http",
      "url": "https://atelier-tools.elya-studio.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ranqint-atelier-tools]
url = "https://atelier-tools.elya-studio.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ranqint-atelier-tools": {
      "type": "remote",
      "url": "https://atelier-tools.elya-studio.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ranqint-atelier-tools --url 'https://atelier-tools.elya-studio.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ranqint-atelier-tools:
    url: "https://atelier-tools.elya-studio.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ranqint-atelier-tools": {
      "Transport": "http",
      "Url": "https://atelier-tools.elya-studio.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ranqint-atelier-tools -t streamable-http -u 'https://atelier-tools.elya-studio.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ranqint-atelier-tools": {
      "type": "http",
      "url": "https://atelier-tools.elya-studio.com/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-21 (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-11-19 (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.

### 2026-11-17 (score 74, +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.

### 2026-11-14 (score 73, +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.

### 2026-11-13 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 72)

First indexed and scored.

## MCP tools (2)

### `plan_studio_website_pages` (~154 tokens)

Plan the pages of an architecture or interior design studio website

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.

Input parameters:

- `journal` (boolean): Whether the studio will write about its work a few times a year. Default false.
- `project_count` (integer): How many projects the studio wants to show on the site. Default 6.
- `studio_type` (string): What the studio designs: buildings (architecture), interiors, or both. Default both.

### `score_studio_website` (~214 tokens)

Score an architecture or interior design studio website

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.

Input parameters:

- `answers` (object): One answer per check: yes, partly or no. Leave out a check that is not known yet.
- `journal` (boolean): Whether the studio will write about its work a few times a year. Default false.
- `project_count` (integer): How many projects the studio wants to show on the site. Default 6.
- `studio_type` (string): What the studio designs: buildings (architecture), interiors, or both. Default both.

## Diagnostics

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

## Score history

- 2026-11-21: 76
- 2026-11-20: 75
- 2026-11-19: 75
- 2026-11-18: 74
- 2026-11-17: 74
- 2026-11-16: 73
- 2026-11-15: 73
- 2026-11-14: 73
- 2026-11-13: 72
- 2026-11-12: 72

## 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.

## Links

- Remote endpoint: https://atelier-tools.elya-studio.com/mcp
- Website: https://atelier-tools.elya-studio.com/chatgpt-claude
- Changelog RSS feed: https://verifymcp.io/servers/ranqint-atelier-tools/atelier-tools.xml
- Changelog JSON feed: https://verifymcp.io/servers/ranqint-atelier-tools/atelier-tools/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ranqint-atelier-tools/atelier-tools.json
- HTML version of this page: https://verifymcp.io/servers/ranqint-atelier-tools/atelier-tools
