ru.layero/layero
up checked
Unclaimed · Unverified
Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.
Publisher-provided title
Layero
Publisher-provided description
Deploy and operate sites on Layero — hosting with build servers in Russia: domains, env, Data API.
Summary by lookupd
Deploys and operates static sites on Russian-hosted build servers: builds, domains, env vars, rollbacks, logs, analytics and checks.
Install
Claude Code, remote (streamable-http)
claude mcp add --transport http layero https://mcp.layero.ru/mcp
Codex, remote (streamable-http)
codex mcp add layero --url https://mcp.layero.ru/mcp
Cursor, remote (streamable-http) → .cursor/mcp.json
{
"mcpServers": {
"layero": {
"url": "https://mcp.layero.ru/mcp"
}
}
}Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.
Tools (showing 30 of 39)
Publisher-provided text
search_docsSearch docs.layero.ru — no token needed. Use it before guessing how the platform works: build settings and `layero.json`, environments and preview URLswhoamiWho 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 cheapermy_projectsThe 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 activelist_sourcesWhich git providers Layero supports and which of them the organization has connected (GitHub App installations and provider tokens). Call before `imporimport_repoCreate 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 bralist_environmentsThe 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 pproject_createCreate an empty project with no repository — an address reserved for a later `publish_site` or `npx layero@latest deploy`. For a project FROM a repositsite_statusHow 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, deplcheck_rulesCheck the published site against Layero's anti-phishing rules (https://layero.ru/rules): collecting passwords, card details or wallet recovery phrases oenv_varsProject environment variables: list names, set them, remove them. VALUES ARE NEVER READ BACK — not by you, not by the platform in its response. Only naproject_settingsBuild settings of a project: read them, or change them without the dashboard — the way out when detection guessed wrong (wrong folder, wrong type, wrongconnect_analyticsConnect 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 tosite_analyticsSite traffic: totals, direction and top sources. The time series is collapsed into a direction and breakdowns are cut to five: ninety chart points arecheck_performanceMeasure 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 deploconnect_domainConnect 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 echeck_domainCheck whether a connected domain has started working. Runs the DNS check immediately instead of waiting for the background re-check. If the records havlist_domainsThe project's own domains and their state.read_siteWhat 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 expsite_screenshotA 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 witsite_issuesConcrete 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 nrefactor_siteOne named markup transformation — with a predictable result. The tool PUBLISHES NOTHING. It returns the changed HTML; showing it to the person, gettingcheck_copyMechanical 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 llist_deploysThe 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_deploydownload_sourceA short download link to a ZIP of what a build was made from. For an upload (`npx layero@latest deploy`) the ZIP holds the uploaded sources; for a siterollbackPut the previous working build back on the live address. CHANGES WHAT VISITORS SEE — ask the person before calling unless they asked for a rollback expretry_deployRun 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 incancel_deployStop a build that is still running. The live address does not change — the previous version stays on it.deploy_logsRaw log lines — for when the `diagnose_deploy` analysis was not enough. Start with `diagnose_deploy`: it has already pulled out the cause and the neighdiagnose_deployWhy 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. Topublish_sitePublish 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
Details
- Version: 2.4.0
- Transports: streamable-http
- Uptime (7 days): 100%
- Median latency: 1838 ms
- First indexed:
- Last seen in registry:
- Repository: https://github.com/LayeroInfra/layero-agents
- Website: https://docs.layero.ru/agents/
Badge for your README
Shows this live status and links here; updates hourly.
[](https://lookupd.com/servers/ru.layero/layero)
- 62033 servers
- Last crawl: 2026-11-11T15:38:39.561Z
- API base:
https://api.lookupd.com - MCP URL:
https://api.lookupd.com/mcp