Atelier Studio Website Tools MCP server
io.github.Ranqint/atelier-toolsRanqintstreamable-httpv1.0.0Scanned
Plan and score the website of an architecture or interior design studio.
2 tools: 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 Atelier Studio Website Tools MCP server can do
The Atelier Studio Website Tools MCP server is published by the GitHub account Ranqint. It has 2 tools. It can create or change data (1 tool: score_studio_website), but cannot delete data. 1 tool only reads.
1 tool brings in text other people can write (plan_studio_website_pages).
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.
Last scanned Nov 12, 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.
2 tools
Changes things 1Claude Code: ask
score_studio_websiteScores 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,…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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Score an architecture or interior design studio website
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 1Show 1 read-only tool
plan_studio_website_pagesLists 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 p…Reads text others writeNo findings
Why it is in this group
- The description's first verb is "list": a word for reading.
What it can reach
- untrusted-inputThe name "plan_studio_website_pages" says "website": it reads web pages, which anyone can write.
- untrusted-inputThe description's first sentence says "list" and "website": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Plan the pages of an architecture or interior design studio website
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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 outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- 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.
Looked at Nov 20, 2026, 18:21 UTC, unchanged since Nov 13, 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
- 1
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://atelier-tools.elya-studio.com/mcp: tools/list returned 2 tools to an anonymous client, including score_studio_website (write)
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.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http atelier-tools https://atelier-tools.elya-studio.com/mcpclaude mcp add --transport http atelier-tools https://atelier-tools.elya-studio.com/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__atelier-tools__plan_studio_website_pages"
],
"ask": [
"mcp__atelier-tools__score_studio_website"
],
"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 atelier-tools. Review it before you use it.
Capability tags behind 1 rule
- mcp__atelier-tools__plan_studio_website_pages untrusted-input
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/io.github.Ranqint/atelier-tools/verify?hash=368bb3a577f44661f51f29bf78b7a93248582a0fa2bbea07e5e8931dec5d9cee" | jq -e '.changed == false'Pinned hash 368bb3a577f4, from Nov 12, 2026, 19:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Ranqint/atelier-tools/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Ranqint/atelier-tools)Source: MCP Registry. Synced Nov 12, 2026, 19:17 UTC.
Atelier Studio Website Tools MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Atelier Studio Website Tools MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 1 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 Atelier Studio Website Tools MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Atelier Studio Website Tools MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Atelier Studio Website Tools MCP server have?
- 2 tools: 1 write, 1 read. score_studio_website and plan_studio_website_pages.
Does the Atelier Studio Website Tools MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Atelier Studio Website Tools MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Atelier Studio Website Tools MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.