Layero
REMOTE · MCP.LAYERO.RU
Deploy and operate sites on Layero — hosting with build servers in Russia: domains, env, Data API.
Available components
Last scanned (19 hours ago)
Scores higher than 98% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Cloud Infrastructure
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 12655 tokens (~308/item across 41 items; 38 tools + 3 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (97% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "retry_deploy" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 40 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.
- 2 Nov 26 0
- “check_performance” added an optional parameter “device” cosmetic
- “check_performance” added an optional parameter “path” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 28 Oct 26 0
- New tool “data_api_auth” functional
- New tool “data_api_buckets” functional
- 27 Oct 26 0
- Tool “data_api_methods” rewrote its description, which is the text the model reads security
- Tool “data_api_status” rewrote its description, which is the text the model reads security
- “project_settings” added an optional parameter “badge” cosmetic
- “data_api_probe” reworded the description of “path” cosmetic
- 26 Oct 26 +53
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Tool “data_api_status” rewrote its description, which is the text the model reads security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 25 Oct 26 −40
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 24 Oct 26 −13
- Authorization: pass → unverified ▼ security
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 22 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Oct 26 +2
- Stability: fail → pass ▲ security
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 5 Nov 2026 · Probed https://mcp.layero.ru/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.layero.ru | CN=YR2,O=Let's Encrypt,C=US | 27 Oct 2026 | 25 Jan 2027 | RSA 2048 | SHA256-RSA | 5bbb049a313fb281805f26c04ec3f52f439 |
| SANs: *.layero.ru, layero.ru | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 mcp.layero.ru. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ru. | DS published | 26734 | 8 | Verified |
| layero.ru. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.layero.ru/.well-known/oauth-protected-resource", scope="read deploy"
Bearer resource_metadata="https://mcp.layero.ru/.well-known/oauth-protected-resource", scope="read deploy"Protected resource metadata
| Document | https://mcp.layero.ru/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.layero.ru/mcp |
| Authorisation server | https://api.layero.ru |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.layero.ru/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.layero.ru/mcp | HTTPS enforced | 301 | https://mcp.layero.ru/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 →
site_status Как дела у сайта ~583
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | 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`. |
| project | string | 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 NO… |
| wait_s | integer | – | 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 cl… |
| Name | Type | Req | Description |
|---|---|---|---|
| answered_by | string | yes | – |
| branch | – | – | – |
| checked_url | string | yes | – |
| http_code | – | yes | – |
| last_deploy_id | – | – | – |
| last_deploy_stage | – | yes | – |
| last_deploy_status | – | yes | – |
| last_error | – | yes | – |
| next_action | string | yes | – |
| platform_screen | – | – | – |
| poll_after_s | – | – | – |
| project | string | yes | – |
| project_type | – | – | – |
| provider | – | – | – |
| redirect_to | – | – | – |
| repo | – | – | – |
| root_directory | – | – | – |
| rules_warnings | – | – | – |
| served_fallback | – | – | – |
| serving | boolean | yes | – |
| source | string | yes | – |
| url | string | yes | – |
| waited_s | – | – | – |
No examples provided.
whoami Кто подключён к Layero ~50
Who is connected to Layero and how many projects they have. Call this first when you are unsure the token is configured: a clear error here is cheaper than one halfway through a deploy.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| – | yes | – | |
| next_action | string | yes | – |
| projects | integer | yes | – |
| username | – | yes | – |
No examples provided.
How do I install the Layero MCP server?
Layero is a hosted endpoint at https://mcp.layero.ru/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 · mcp.layero.ru
claude mcp add --transport http ru-layero-layero 'https://mcp.layero.ru/mcp'
What is the Layero MCP server?
Layero is an MCP server listed in the public MCP registry as ru.layero/layero. Deploy and operate sites on Layero, hosting with build servers in Russia: domains, env, Data API. This page covers its hosted endpoint (https://mcp.layero.ru/mcp).
Is the Layero MCP server safe to use?
Layero scores 90 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 Layero MCP server expose?
Layero exposes 38 tools: search_docs, whoami, my_projects, list_sources, import_repo, and 33 more. Their descriptions and schemas cost roughly 11,169 tokens of context every time the server is loaded.
Does the Layero MCP server require authentication?
Yes. Layero asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Layero MCP server still maintained?
Layero is still listed as active in the MCP registry. We last reached this channel on 5 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 Layero MCP server?
VerifyMCP ran 13 checks on Layero, 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.