check_performance — Layero MCP Tool Read-only
check_performance
(check performance) is one of 35 tools on the
Layero
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_performance from your client
- Claude Code Layero check_performance run in your project directory
- Claude Desktop Layero check_performance ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Layero check_performance ~/.cursor/mcp.json
- VS Code Layero check_performance .vscode/mcp.json
- Zed Layero check_performance ~/.config/zed/settings.json
- Windsurf Layero check_performance ~/.codeium/windsurf/mcp_config.json
- Cline Layero check_performance ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Layero check_performance ~/.gemini/settings.json
- Grok Layero check_performance .mcp.json (in your project root)
- ChatGPT Layero check_performance Settings → Connectors → Advanced → Developer mode
- Claude.ai Layero check_performance Settings → Connectors → Add custom connector
- LangChain Layero check_performance pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http layero https://mcp.layero.ru/mcp
Other tools on this server
- search_docs
- whoami
- my_projects
- list_sources
- import_repo
- list_environments
- project_create
- site_status
- env_vars
- project_settings
- connect_analytics
- site_analytics
- 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
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.