Is ru.layero/layero up? Live MCP status
Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.
| Endpoint | https://mcp.layero.ru/mcp |
|---|---|
| Page built |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Not published (HTTP 404)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://mcp.layero.ru/mcp/server-card |
| MCP server card (SEP-1649 location) | Not published (HTTP 404)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://mcp.layero.ru with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 36 tools: cancel_deploy, check_copy, check_domain, check_performance, check_rules, connect_analytics, connect_domain, data_api_grant, data_api_keys, data_api_methods, data_api_origins, data_api_probe, data_api_status, deploy_logs, diagnose_deploy, env_vars, import_repo, list_deploys, list_domains, list_environments, list_sources, my_projects, project_create, project_settings, publish_landing, publish_site, read_site, refactor_site, retry_deploy, rollback, search_docs, site_analytics, site_issues, site_screenshot, site_status, whoami.
Its tools changed between 2026-09 and 2026-10:
- Added (14):
check_rules,data_api_grant,data_api_keys,data_api_methods,data_api_origins,data_api_probe,data_api_status,import_repo,list_environments,list_sources,project_create,project_settings,publish_site,search_docs - Removed (5):
add_integration,compose_landing,compose_landing_submit,list_design_systems,list_structures cancel_deploy: description, input schema changedcheck_copy: description, input schema, output schema changedcheck_domain: input schema changedcheck_performance: input schema changedconnect_analytics: input schema changedconnect_domain: input schema changeddeploy_logs: description, input schema, output schema changeddiagnose_deploy: description, input schema, output schema changedenv_vars: input schema changedlist_deploys: description, input schema, output schema changedlist_domains: input schema changedmy_projects: description, input schema, output schema changedpublish_landing: description, input schema, output schema changedread_site: description, input schema, output schema changedrefactor_site: description, input schema changedretry_deploy: description, input schema changedrollback: description, input schema changedsite_analytics: input schema, output schema changedsite_issues: description, input schema, output schema changedsite_screenshot: description, input schema changedsite_status: description, input schema, output schema changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | ru.layero/layero |
|---|---|
| Endpoint | https://mcp.layero.ru/mcp |
| Publisher repository | not known: the registry did not return this listing within 4 seconds |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt