Skip to content

Elya Studio MCP server

io.github.Ranqint/elya-studioRanqintstreamable-httpv1.0.1Scanned

For founders in Israel: size a first product version (MVP) and check a development quote.

2 tools: 1 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 1 write, 1 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 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.
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 Elya Studio MCP server can do

The Elya Studio MCP server is published by the GitHub account Ranqint. It has 2 tools. It can create or change data (1 tool: mvp_scope_sizer), but cannot delete data. 1 tool only reads.

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.

Last scanned Nov 14, 2026, version 1.0.1.

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
  • mvp_scope_sizerSuggests the scope of the first version of a planned software product from up to 7 answers: what is being built (web app or SaaS, marketplace, app for the Apple and Google stores, …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
    Suggests the scope of the first version of a planned software product from up to 7 answers: what is being built (web app or SaaS, marketplace, app for the Apple and Google stores, internal business system), the stage, number of user types, an AI feature, payments, integrations and the deadline. Returns the starting tier that fits (clickable prototype, MVP live, MVP with AI and Israeli payments, or a scope that needs a written quote), its timeline, why, and what goes into the first version versus what waits for the next one, in Hebrew. Use when a founder asks what an MVP for their idea should include, how long a first version takes, or what to leave for later. Answers may be given as the ids below or in Hebrew.

    Annotations the server declares

    • title: Size the first version (MVP) of a software product
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • development_quote_checklistLists, in Hebrew, the 8 things a quote for building an app or software should state in writing: what is in the first version and what is not, fixed price or hourly, payment by stag…No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    Lists, in Hebrew, the 8 things a quote for building an app or software should state in writing: what is in the first version and what is not, fixed price or hourly, payment by stages, timeline, who owns the code and the store accounts, maintenance after launch, how scope changes are handled, and who actually builds. For each: why it matters and the question to ask the vendor when it is missing. Pass the items the quote already covers to get back only what is missing. Use when someone received a development quote, or several quotes far apart, and wants to know what to check before signing. It gives no verdict on whether a quote is fair, and it is not legal advice.

    Annotations the server declares

    • title: What a software development quote should include
    • 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 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 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.

    Matched text

    https://strategy.elya-studio.com/mcp: tools/list returned 2 tools to an anonymous client, including mvp_scope_sizer (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.

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.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http elya-studio https://strategy.elya-studio.com/mcp
claude mcp add --transport http elya-studio https://strategy.elya-studio.com/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__elya-studio__development_quote_checklist"
    ],
    "ask": [
      "mcp__elya-studio__mvp_scope_sizer"
    ],
    "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 elya-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/io.github.Ranqint/elya-studio/verify?hash=fe006b7ffcc035f897817fba44ac3ca8a1c34827d5fd9eb3577fd7980c76ccc2" | jq -e '.changed == false'

Pinned hash fe006b7ffcc0, from Nov 14, 2026, 20: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/elya-studio/changes.xml

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

Badge

Anlyon Radar badge for io.github.Ranqint/elya-studio
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Ranqint/elya-studio.svg)](https://radar.anlyon.com/servers/io.github.Ranqint/elya-studio)

Source: MCP Registry. Synced Nov 14, 2026, 20:17 UTC.

Elya Studio MCP server: questions and answers

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

Is the Elya Studio 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 Elya 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 Elya Studio 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 Elya Studio MCP server have?

2 tools: 1 write, 1 read. mvp_scope_sizer and development_quote_checklist.

Does the Elya Studio MCP server need sign-in or OAuth?

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

Does the Elya 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 Elya Studio MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.