Layero

This connector has been deprecated

Duplicate listing of the same server under an old namespace. The maintained listing is Layero (ru.layero/layero): same endpoint https://mcp.layero.ru/mcp, current description and tools. The landing-page generator described here was removed in MCP 2.0.

Как дела у сайта

site_status

Read-only

How a site is doing: where it is built from, whether the address is answering, and how the latest build ended.

One call instead of three (project, deploys, live check of the address).
`source` / `repo` / `branch` / `root_directory` say where the project is
built from — a connected repository means deploys go through git.

`serving` is true when the SITE ITSELF answered — any response that is
not a Layero platform screen and not a 5xx. An API server that has no
`/` route answers with its own 404: that is a running app, not a broken
site — check a real route with `path`. `answered_by` tells who replied:
`site`, `platform` (a Layero screen, named in `platform_screen`:
`unavailable`, `coming-soon`, `starting`, `not-found`, `suspended`) or
`none` (no response). Redirects are not followed: `redirect_to` shows
the target.

Waiting for a build: while the latest build is running the answer carries
`poll_after_s` — call again after that many seconds. Or pass `wait_s` and
the server waits for the build itself (mind your client's tool-call
timeout, see the argument). `waited_s` says how long the call waited.

Static sites: `served_fallback: true` means the requested `path` was
answered with the HOME page (a missing file is replaced by `index.html`
with code 200) — the address answers, but this page does not exist.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	No	Path to check on the site, from its root. Default `/`. For an API server with no `/` route pass a route that exists, e.g. `/api/health` or `/healthz`.	/
`wait_s`	No	Wait for a running build: if the latest build is queued/building, the call holds until it finishes or `wait_s` seconds pass, then answers as usual. Default 0 — answer at once. At most 120. 🚨 Your client has its own tool-call timeout, often 60 s (Cursor, Codex): stay under it — 45 is safe everywhere — or the call is cut on your side while the build carries on. Still building afterwards → call again.
`project`	Yes	The project: its slug (`my-site`) or id, as listed by `my_projects`. The site address works too (`https://clear-garden-vypm.layero.app` or just `clear-garden-vypm`) — note that the address host is NOT always the slug.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`repo`	No
`branch`	No
`source`	Yes
`project`	Yes
`serving`	Yes
`provider`	No
`waited_s`	No
`http_code`	Yes
`last_error`	Yes
`answered_by`	Yes
`checked_url`	Yes
`next_action`	Yes
`redirect_to`	No
`poll_after_s`	No
`project_type`	No
`last_deploy_id`	No
`root_directory`	No
`rules_warnings`	No
`platform_screen`	No
`served_fallback`	No
`last_deploy_stage`	Yes
`last_deploy_status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 29, 2026

addedOutput schema / $defs

Added value: +{
+  "RulesWarning": {
+    "properties": {
+      "explanation": {
+        "title": "Explanation",
+        "type": "string"
+      },
+      "rule": {
+        "title": "Rule",
+        "type": "string"
+      },
+      "title": {
+        "title": "Title",
+        "type": "string"
+      },
+      "url": {
+        "title": "Url",
+        "type": "string"
+      }
+    },
+    "required": [
+      "rule",
+      "title",
+      "explanation",
+      "url"
+    ],
+    "title": "RulesWarning",
+    "type": "object"
+  }
+}

addedOutput schema / properties / rules_warnings

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "$ref": "#/$defs/RulesWarning"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Rules Warnings"
+}

Changed5 schema fields changedSep 19, 2026

addedInput schema / properties / wait_s

Added value: +{
+  "default": 0,
+  "description": "Wait for a running build: if the latest build is queued/building, the call holds until it finishes or `wait_s` seconds pass, then answers as usual. Default 0 — answer at once. At most 120. 🚨 Your client has its own tool-call timeout, often 60 s (Cursor, Codex): stay under it — 45 is safe everywhere — or the call is cut on your side while the build carries on. Still building afterwards → call again.",
+  "title": "Wait S",
+  "type": "integer"
+}

addedOutput schema / properties / last_deploy_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Last Deploy Id"
+}

addedOutput schema / properties / poll_after_s

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Poll After S"
+}

addedOutput schema / properties / served_fallback

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Served Fallback"
+}

addedOutput schema / properties / waited_s

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Waited S"
+}

Changed13 schema fields changedSep 18, 2026

addedInput schema / properties / path

Added value: +{
+  "default": "/",
+  "description": "Path to check on the site, from its root. Default `/`. For an API server with no `/` route pass a route that exists, e.g. `/api/health` or `/healthz`.",
+  "title": "Path",
+  "type": "string"
+}

changedInput schema / properties / project / description

Previous value: -"Проект: слаг (`my-site`) или id. Слаг — то, что видно в адресе сайта; если пользователь назвал сайт словами, возьми слаг из `my_projects`."New value: +"The project: its slug (`my-site`) or id, as listed by `my_projects`. The site address works too (`https://clear-garden-vypm.layero.app` or just `clear-garden-vypm`) — note that the address host is NOT always the slug."

addedOutput schema / properties / answered_by

Added value: +{
+  "enum": [
+    "site",
+    "platform",
+    "none"
+  ],
+  "title": "Answered By",
+  "type": "string"
+}

addedOutput schema / properties / branch

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Branch"
+}

addedOutput schema / properties / checked_url

Added value: +{
+  "title": "Checked Url",
+  "type": "string"
+}

addedOutput schema / properties / platform_screen

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Platform Screen"
+}

addedOutput schema / properties / project_type

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Project Type"
+}

addedOutput schema / properties / provider

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Provider"
+}

addedOutput schema / properties / redirect_to

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Redirect To"
+}

addedOutput schema / properties / repo

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Repo"
+}

addedOutput schema / properties / root_directory

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Root Directory"
+}

addedOutput schema / properties / source

Added value: +{
+  "enum": [
+    "git",
+    "cli"
+  ],
+  "title": "Source",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "project",
-  "url",
-  "serving",
-  "http_code",
-  "last_deploy_status",
-  "last_deploy_stage",
-  "last_error",
-  "next_action"
-]New value: +[
+  "project",
+  "url",
+  "source",
+  "serving",
+  "checked_url",
+  "http_code",
+  "answered_by",
+  "last_deploy_status",
+  "last_deploy_stage",
+  "last_error",
+  "next_action"
+]

Changed1 schema field changedAug 3, 2026

addedInput schema / properties / project / description

Added value: +"Проект: слаг (`my-site`) или id. Слаг — то, что видно в адресе сайта; если пользователь назвал сайт словами, возьми слаг из `my_projects`."

AddedJul 27, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare readOnlyHint=true, but the description discloses a rich behavioral model: serving semantics (non-platform, non-5xx), answered_by values, the platform_screen enum states, that redirects are NOT followed, poll_after_s polling, waited_s, and served_fallback for static index replacement. This is exactly the kind of context the annotation cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well front-loaded: the lead sentence gives the whole purpose, then paragraphs break out source, serving, build-waiting and static fallback. It is on the long side, but each block covers a distinct behavior; nothing is clearly redundant enough to drop.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values need not be explained, yet the description describes them anyway (serving, answered_by, platform_screen, redirect_to, served_fallback). Combined with the polling guidance and timeout warning, an agent has everything needed to call and interpret this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents project, path and wait_s in depth; the baseline is 3. The description reinforces the path-for-API-servers case and the wait_s client-timeout hazard, but largely restates schema content rather than adding net-new parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource ('How a site is doing') and enumerates the three facts it returns: build source, whether the address answers, and how the latest build ended. The parenthetical 'One call instead of three (project, deploys, live check of the address)' clearly positions it against the sibling families my_projects, list_deploys and check_domain.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Strong implicit routing: the 'one call instead of three' line tells the agent to consolidate project/deploy/live checks here rather than calling the individual siblings. It also explains the poll_after_s vs wait_s decision and when to re-call. It does not name a single sibling tool explicitly, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Layero tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?