MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Code & DevOps

Elya Studio

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

Checks passed
12 / 22

2 failed · 8 not measured

Median response
1041 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
2

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Last checked . Not enough checks yet
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
400
Publisher identityCan the publisher be traced to its source?
222

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 1041 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name elya.

  • Pass
    Lists tools

    tools/list returned 2 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 1041 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 1041 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    8 of 8 parameters have a description (100%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Not measured
    Website matches publisher

    This namespace is not a reverse domain, so the website comparison does not apply.

  • Fail
    Source repo linked

    No repository URL is on file.

  • Fail
    Repo owner matches

    The GitHub repository owner does not match the namespace login.

  • Pass
    Recently updated

    Updated 2026-11-12T17:07:16.499338Z, within 180 days.

  • Not measured
    Open-source licence

    No GitHub repository to ask about a licence.

Start using Elya Studio

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

claude mcp add --transport http elya-studio https://strategy.elya-studio.com/mcp

Capabilities

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.

Discovered
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.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 90 days.
CheckedResultResponseTools
Connected1041 ms2