Developer · Remote MCP server
Layero
Deploy and operate sites on Layero - hosting with build servers in Russia: domains, env, Data API.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ru.layero/layero- Version
- 2.4.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-19
- Updated
- 2026-09-19
- Publisher
- ru.layero
- Namespace
- Namespace verified by the MCP Registry via the domain layero.ru · how
- Website
- docs.layero.ru/agents/
- Repository
- github.com/LayeroInfra/layero-agents
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.layero.ru/mcp | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- layero 2.5.0 · protocol 2025-06-18
- Tools discovered
36 - show names
search_docs,whoami,my_projects,list_sources,import_repo,list_environments,project_create,site_status,check_rules,env_vars,project_settings,connect_analytics,site_analytics,check_performance,connect_domain,check_domain,list_domains,read_site,site_screenshot,site_issues,refactor_site,check_copy,list_deploys,rollback,retry_deploy,cancel_deploy,deploy_logs,diagnose_deploy,publish_site,publish_landing,data_api_status,data_api_methods,data_api_grant,data_api_keys,data_api_origins,data_api_probe- Checked on
- 2026-10-05
How to connect Layero
Layero is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.layero.ru/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Latitude 10 StoreDeveloper kits and design packs for AI agents, paid in USDC over x402. Free API readiness check. | Remote · HTTPLive check: ✓ handshake |
| LaunchFlagFeature flags and kill switches. Turn a shipped feature off in production without a deploy. | Remote & Local · HTTP, stdioLive check: sign-in required |
| LaunchTrustCompliance & security scan for your app: secrets, exposed files, headers, privacy, AI-disclosure. | Remote · HTTPLive check: ✓ handshake |
| Lawang OnboardPermission-aware onboarding MCP server: answers about a codebase, filtered by the caller's role. | Remote & Local · HTTP, stdioLive check: sign-in required |
| LazywebReal product evidence: 281k+ real app screens and flows, 20k+ mobile A/B tests, growth reports. | Remote · HTTPLive check: sign-in required |
| LBrainLocal-first agent memory. Source, date, bind/abstain. Permanent name: lbrain.ai/claim.html. | Local · stdio |
| LDAP Assistant MCPMCP server for 389 Directory Server health diagnostics, log analysis, and SOS-report investigation. | Local · stdio |
| LeakRank GuardScans code changes for leaked secrets and insecure config, with actionable fixes for AI agents. | Local · stdio |