Elya Studio is an MCP server published by io.github.Ranqint, hosted at strategy.elya-studio.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 2 tools, including mvp_scope_sizer, development_quote_checklist.
For founders in Israel: size a first product version (MVP) and check a development quote.
875 connections through 4 shared values. Tap any node.
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.
| Parameter | Type | Description |
|---|---|---|
| ai | string | An AI feature inside the product (chat, document analysis, text or image generation), optional. no = לא; yes = כן, פיצ'ר AI בעברית |
| pay | string | Payments in the first version, optional. none = בלי תשלום בגרסה הראשונה; card = תשלום בכרטיס (Stripe); il = סליקה ישראלית |
| type |
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
| string |
| What is being built. web = אפליקציית ווב או SaaS; market = מרקטפלייס: קונים ומוכרים; store = אפליקציה לחנויות (אפל וגוגל); internal = מערכת פנימית לעסק; unsure = עוד לא בטוחים |
| when | string | When it must be live, optional. 2w = תוך שבועיים; 1m = תוך חודש; 2m = תוך חודשיים; flex = אין תאריך קבוע |
| roles | string | How many types of users (e.g. customer and admin = 2), optional. 1 = סוג אחד; 2 = שניים; 3 = 3 ומעלה |
| stage | string | Where the founder is today, optional. idea = יש רעיון, עוד לא דיברנו עם לקוחות; talked = דיברנו עם לקוחות, צריך משהו להראות; demand = יש לקוחות שמחכים או מוכנים לשלם |
| integrations | array | Existing systems to connect, any number, optional. whatsapp = וואטסאפ; crm = CRM; invoices = מערכת חשבוניות; calendar = יומן; other = מערכת אחרת שכבר יש לכם |
{
"name": "mvp_scope_sizer",
"title": "Size the first version (MVP) of a software product",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"type"
],
"properties": {
"ai": {
"type": "string",
"description": "An AI feature inside the product (chat, document analysis, text or image generation), optional. no = לא; yes = כן, פיצ'ר AI בעברית"
},
"pay": {
"type": "string",
"description": "Payments in the first version, optional. none = בלי תשלום בגרסה הראשונה; card = תשלום בכרטיס (Stripe); il = סליקה ישראלית"
},
"type": {
"type": "string",
"description": "What is being built. web = אפליקציית ווב או SaaS; market = מרקטפלייס: קונים ומוכרים; store = אפליקציה לחנויות (אפל וגוגל); internal = מערכת פנימית לעסק; unsure = עוד לא בטוחים"
},
"when": {
"type": "string",
"description": "When it must be live, optional. 2w = תוך שבועיים; 1m = תוך חודש; 2m = תוך חודשיים; flex = אין תאריך קבוע"
},
"roles": {
"type": "string",
"description": "How many types of users (e.g. customer and admin = 2), optional. 1 = סוג אחד; 2 = שניים; 3 = 3 ומעלה"
},
"stage": {
"type": "string",
"description": "Where the founder is today, optional. idea = יש רעיון, עוד לא דיברנו עם לקוחות; talked = דיברנו עם לקוחות, צריך משהו להראות; demand = יש לקוחות שמחכים או מוכנים לשלם"
},
"integrations": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 5,
"description": "Existing systems to connect, any number, optional. whatsapp = וואטסאפ; crm = CRM; invoices = מערכת חשבוניות; calendar = יומן; other = מערכת אחרת שכבר יש לכם"
}
},
"additionalProperties": false
},
"annotations": {
"title": "Size the first version (MVP) of a software product",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| covered | array | Items the quote already states in writing, optional. scope = מה נכנס לגרסה הראשונה, ומה לא; pricing_model = מחיר קבוע או לפי שעות; payment_stages = תשלום לפי שלבים; timeline = לוח זמנים; ownership = של מי הקוד והחשבונות; maintenance = תחזוקה אחרי ההשקה; scope_change = שינוי בהיקף באמצע; who_builds =… |
{
"name": "development_quote_checklist",
"title": "What a software development quote should include",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"covered": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 8,
"description": "Items the quote already states in writing, optional. scope = מה נכנס לגרסה הראשונה, ומה לא; pricing_model = מחיר קבוע או לפי שעות; payment_stages = תשלום לפי שלבים; timeline = לוח זמנים; ownership = של מי הקוד והחשבונות; maintenance = תחזוקה אחרי ההשקה; scope_change = שינוי בהיקף באמצע; who_builds = מי בונה בפועל"
}
},
"additionalProperties": false
},
"annotations": {
"title": "What a software development quote should include",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Two tools from Elya Studio, a product studio: sizing the first version (MVP) of a software product, and the checklist of what a development quote should include. Results are in Hebrew; links point to the full tools on elya-studio.com.
Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.