Layero

Name: Layero
Author: ru.layero

MCP serverMCP

Deploy and operate sites on Layero — hosting with build servers in Russia: domains, env, Data API.

by ru.layerorepository ↗homepage ↗v2.4.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"layero","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability (some checks stopped at authentication)109/109 checks ok

Some successful checks reached the service and some stopped at an authentication response; figures combine both.

when	check	result	http	latency	detail
7 h ago	mcp initialize	ok	200	55 ms	server layero 2.5.0 · protocol 2025-06-18 · 36 tools
13 h ago	mcp initialize	ok	200	74 ms	server layero 2.5.0 · protocol 2025-06-18 · 36 tools
19 h ago	mcp initialize	ok	200	55 ms	server layero 2.5.0 · protocol 2025-06-18 · 36 tools
25 h ago	mcp initialize	ok	200	54 ms	server layero 2.5.0 · protocol 2025-06-18 · 36 tools
32 h ago	mcp initialize	ok	200	57 ms	server layero 2.5.0 · protocol 2025-06-18 · 36 tools
2 d ago	mcp initialize	ok	200	85 ms	server layero 2.5.0 · protocol 2025-06-18 · 36 tools
2 d ago	mcp initialize	ok	200	54 ms	server layero 2.5.0 · protocol 2025-06-18 · 36 tools
2 d ago	mcp initialize	ok	200	54 ms	server layero 2.5.0 · protocol 2025-06-18 · 36 tools
2 d ago	mcp initialize	ok	200	53 ms	server layero 2.5.0 · protocol 2025-06-18 · 36 tools
3 d ago	mcp initialize	ok	200	60 ms	server layero 2.5.0 · protocol 2025-06-18 · 36 tools

Tools observed via MCP handshake

search_docs — Search docs.layero.ru — no token needed. Use it before guessing how the platform works: build settings and `layero.json`, environments and preview URLs
whoami — 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
my_projects — The user's sites on Layero. Thirty most recent by default. The full list is rarely needed, while flooding half your context with it is easy: an active
list_sources — Which git providers Layero supports and which of them the organization has connected (GitHub App installations and provider tokens). Call before `impor
import_repo — Create a Layero project from a repository — path (a) without the dashboard. From then on a push to the branch is a preview, a push to the production bra
list_environments — The project's environments — one per branch (or the single `cli` one), each with its address and the state of its latest build. Answers "where is the p
project_create — Create an empty project with no repository — an address reserved for a later `publish_site` or `npx layero@latest deploy`. For a project FROM a reposit
site_status — 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, depl
check_rules — Check the published site against Layero's anti-phishing rules (https://layero.ru/rules): collecting passwords, card details or wallet recovery phrases o
env_vars — Project environment variables: list names, set them, remove them. VALUES ARE NEVER READ BACK — not by you, not by the platform in its response. Only na
project_settings — Build settings of a project: read them, or change them without the dashboard — the way out when detection guessed wrong (wrong folder, wrong type, wrong
connect_analytics — Connect Yandex Metrika to a site. IMPORTANT: authorisation happens IN A BROWSER, and neither you nor the platform can do that step for the user. The to
site_analytics — Site traffic: totals, direction and top sources. The time series is collapsed into a direction and breakdowns are cut to five: ninety chart points are
check_performance — Measure a site's speed and say whether it got worse after a deploy. The verdict comes FROM THE SCORE, not from timings: repeated runs of the same deplo
connect_domain — Connect a custom domain to a site. IMPORTANT: between this call and a working domain stands A PERSON. You get DNS records — show them to the user and e
check_domain — Check whether a connected domain has started working. Runs the DNS check immediately instead of waiting for the background re-check. If the records hav
list_domains — The project's own domains and their state.
read_site — What is really published: headings, copy, forms, meta, links. Call it BEFORE changing anything on a live site and AFTER a publish, to make sure the exp
site_screenshot — A screenshot of the latest built version of the site — how it looks. Complements `read_site` (what is on the page) and `site_issues` (what is wrong wit
site_issues — Concrete problems of a page — each with its location and what to do. This is NOT a score. The score comes from `check_performance`, and a score gives n
refactor_site — One named markup transformation — with a predictable result. The tool PUBLISHES NOTHING. It returns the changed HTML; showing it to the person, getting
check_copy — Mechanical errors of Russian typography — with the exact place and a replacement. This is CODE, not a model's judgement: the same text gives the same l
list_deploys — The project's latest builds: how each one ended, how long it took and which one is live now. Use it to pick a target for `rollback` or `diagnose_deploy
rollback — Put the previous working build back on the live address. CHANGES WHAT VISITORS SEE — ask the person before calling unless they asked for a rollback exp
retry_deploy — Run a build again — a failed one as is, or the latest commit afresh. Default (`redeploy=false`): queue the SAME build again. Allowed only for builds in
cancel_deploy — Stop a build that is still running. The live address does not change — the previous version stays on it.
deploy_logs — Raw log lines — for when the `diagnose_deploy` analysis was not enough. Start with `diagnose_deploy`: it has already pulled out the cause and the neigh
diagnose_deploy — Why a deploy failed — with the cause parsed out, not a raw log. Without `deploy` the latest build is used; that is what reflects the current state. To
publish_site — Publish a static site to Layero — from here, with no terminal. Takes ANY ready static bundle, so it is the answer to "deploy my site" when the project
publish_landing — DEPRECATED — use `publish_site`. Same behaviour, same arguments. Kept for one release (removed in the next) so that configs and prompts written before
data_api_status — Whether the database has the Data API enabled, its address, keys and the sites allowed to call it. Keys are shown as prefixes only: the platform never
data_api_methods — The database's REST and RPC methods with an access level per HTTP method. The level says who may call the method: closed, visitor (any site visitor), u
data_api_grant — Who may call a method of a table or a function: shows the SQL and applies it after consent. OPENS DATA TO THE INTERNET. Call it without `apply` first:
data_api_keys — The database's Data API keys: list, issue, revoke. The list never contains key values. Issuing and revoking need the person's consent: a client with fo
data_api_origins — Sites allowed to call the database from a browser: list, add, remove. Addresses of the connected projects and their branches are allowed automatically
data_api_probe — A real request to a method through the gateway — as a visitor, a user or the server. The platform supplies the key and the token. Writes (POST, PATCH,

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryru.layero/layero

first seen 1 mo ago · fetched 30 h agoopen ↗

Field history (12 recent events)

20 d ago · declared · version → "2.4.0"
22 d ago · declared · summary → "Deploy and operate sites on Layero — hosting with build servers in Russia: domains, env, Data API."
22 d ago · declared · description → "Deploy and operate sites on Layero — hosting with build servers in Russia: domains, env, Data API."
22 d ago · declared · homepageUrl → "https://docs.layero.ru/agents/"
22 d ago · declared · repoUrl → "https://github.com/LayeroInfra/layero-agents"
22 d ago · declared · version → "2.1.0"
1 mo ago · declared · summary → "Build a landing page from your IDE chat, publish it, then manage domains and analytics."
1 mo ago · declared · protocols → ["mcp"]
1 mo ago · declared · description → "Build a landing page from your IDE chat, publish it, then manage domains and analytics."
1 mo ago · declared · publisherName → "ru.layero"
1 mo ago · declared · homepageUrl → "https://docs.layero.ru/en/plugin/intro/"
1 mo ago · declared · repoUrl → "https://github.com/LayeroInfra/layero-claude"

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from