# Elya Studio

> Size a first product version (MVP) and check what a development quote should state.

- name: io.github.Ranqint/elya-studio
- 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%2Felya-studio
- tools: https://api.protogrid.dev/v1/servers/io.github.Ranqint%2Felya-studio/tools

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

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "elya-studio": {
      "type": "http",
      "url": "https://strategy.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 890 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 890 tokens to load them all
- tool set hash: d265eb9be0386519cbf7334900f3590a
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.Ranqint/elya-studio.svg)](https://protogrid.dev/servers/io.github.Ranqint/elya-studio)
- 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://strategy.elya-studio.com/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (2)

- `development_quote_checklist`: 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.
- `mvp_scope_sizer`: 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.