# Atelier Studio Website Tools

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

- name: io.github.Ranqint/atelier-tools
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 80/100 flags: no-repository
- quality: 89/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.Ranqint%2Fatelier-tools
- tools: https://api.protogrid.dev/v1/servers/io.github.Ranqint%2Fatelier-tools/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 45
- drivers: +website +reachable +uptime-100% +updated-2d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 89/100 (new)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 2 of 2 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 1,126 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump
- pass `tools.hidden_text`: no hidden text in tool names, descriptions, schemas or annotations

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`, `stability.new_links`: tool history recorded for 1 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 2, about 1,126 tokens to load them all
- tool set hash: af6570fa01bc723a7c4d51ef235d5513
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.Ranqint/atelier-tools.svg)](https://protogrid.dev/servers/io.github.Ranqint/atelier-tools)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://atelier-tools.elya-studio.com/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (2)

- `plan_studio_website_pages`: 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.
- `score_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.