Elya Studio
REMOTE · STRATEGY.ELYA-STUDIO.COM
For founders in Israel: size a first product version (MVP) and check a development quote.
Available components
Last scanned (23 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability55
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 816 tokens (~408/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Nov 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://strategy.elya-studio.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=strategy.elya-studio.com | CN=YR1,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | RSA 2048 | SHA256-RSA | 6424571a7a5ba572a78caa027bbadb87283 |
| SANs: strategy.elya-studio.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of strategy.elya-studio.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| elya-studio.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | base-uri 'self'; object-src 'none'; frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://strategy.elya-studio.com/mcp | Verified | 200 | |
| http (plaintext) | http://strategy.elya-studio.com/mcp | HTTPS enforced | 308 | https://strategy.elya-studio.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
development_quote_checklist What a software development quote should include ~248
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.
| Name | Type | Req | Description |
|---|---|---|---|
| covered | array | – | Items the quote already states in writing, optional. scope = מה נכנס לגרסה הראשונה, ומה לא; pricing_model = מחיר קבוע או לפי שעות; payment_stages = תשלום לפי שלבים; timeline = לוח זמנים; ownership =… |
No output schema declared.
No examples provided.
mvp_scope_sizer Size the first version (MVP) of a software product ~512
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ai | string | – | An AI feature inside the product (chat, document analysis, text or image generation), optional. no = לא; yes = כן, פיצ'ר AI בעברית |
| integrations | array | – | Existing systems to connect, any number, optional. whatsapp = וואטסאפ; crm = CRM; invoices = מערכת חשבוניות; calendar = יומן; other = מערכת אחרת שכבר יש לכם |
| pay | string | – | Payments in the first version, optional. none = בלי תשלום בגרסה הראשונה; card = תשלום בכרטיס (Stripe); il = סליקה ישראלית |
| 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 = יש לקוחות שמחכים או מוכנים לשלם |
| type | string | yes | What is being built. web = אפליקציית ווב או SaaS; market = מרקטפלייס: קונים ומוכרים; store = אפליקציה לחנויות (אפל וגוגל); internal = מערכת פנימית לעסק; unsure = עוד לא בטוחים |
| when | string | – | When it must be live, optional. 2w = תוך שבועיים; 1m = תוך חודש; 2m = תוך חודשיים; flex = אין תאריך קבוע |
No output schema declared.
No examples provided.
How do I install the Elya Studio MCP server?
Elya Studio is a hosted endpoint at https://strategy.elya-studio.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · strategy.elya-studio.com
claude mcp add --transport http ranqint-elya-studio 'https://strategy.elya-studio.com/mcp'
What is the Elya Studio MCP server?
Elya Studio is an MCP server listed in the public MCP registry as io.github.Ranqint/elya-studio. For founders in Israel: size a first product version (MVP) and check a development quote. This page covers its hosted endpoint (https://strategy.elya-studio.com/mcp).
Is the Elya Studio MCP server safe to use?
Elya Studio scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Elya Studio MCP server expose?
Elya Studio exposes 2 tools: mvp_scope_sizer, development_quote_checklist. Their descriptions and schemas cost roughly 760 tokens of context every time the server is loaded.
Does the Elya Studio MCP server require authentication?
No. We connected to Elya Studio without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Elya Studio MCP server still maintained?
Elya Studio is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Elya Studio MCP server?
VerifyMCP ran 13 checks on Elya Studio, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.