Deploy and operate sites on Layero — hosting with build servers in Russia: domains, env, Data API. [Layero](https://layero.ru) is a deployment and hosting platform. The MCP server covers the whole lifecycle: publish a static bundle, import a repository (GitHub, GitVerse, GitLab, GitFlic, SourceCraft) with an automatic first build, check deploy status and logs, roll back, manage custom domains, environment variables, Yandex Metrica analytics and a Postgres Data API. Sign in via OAuth in the client; `Authorization: Bearer $LAYERO_TOKEN` for CI. **Tools (34):** sources — `list_sources`, `import_repo`, `project_create`, `list_environments`; publish — `publish_site`; operate — `site_status`, `list_deploys`, `diagnose_deploy`, `deploy_logs`, `rollback`, `retry_deploy`, `cancel_deploy`; site — `read_site`, `site_issues`, `site_screenshot`, `refactor_site`, `check_copy`, `check_performance`; setup — `env_vars`, `connect_domain`, `check_domain`, `list_domains`; analytics — `connect_analytics`, `site_analytics`; Data API — `data_api_status`, `data_api_methods`, `data_api_grant`, `data_api_keys`, `data_api_origins`, `data_api_probe`; account — `whoami`, `my_projects`; docs — `search_docs`. Docs: https://docs.layero.ru/agents/ · Skill and install commands: https://github.com/LayeroInfra/layero-agents > Not to be confused with Layer0 / Edgio, or with layero.com — unrelated products.
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C, 47.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 7/10 | initialize answered; tools/list failed.
|
| Live MCP endpoint | 24/25 | Endpoint answers the MCP initialize handshake (2861 ms); slow response -1. |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 39 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,021 reachable MCP servers in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.
- Readiness
- Higher than 60% of peers
- This listing 83 · peer median 81
- Latency
- Faster than 5% of peers
- This listing 1,366 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Valid MCP handshake −3
— Complete the MCP handshake without errors.
Now: initialize answered; tools/list failed.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/borisowvalia/layero/mcpcurl -X POST https://server.smithery.ai/borisowvalia/layero/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'