check_rent_control_perimeter — Miramo MCP Tool Read-only
check_rent_control_perimeter
(check rent control perimeter) is one of 6 tools on the
Miramo
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_rent_control_perimeter from your client
- Claude Code Miramo check_rent_control_perimeter run in your project directory
- Claude Desktop Miramo check_rent_control_perimeter ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Miramo check_rent_control_perimeter ~/.cursor/mcp.json
- VS Code Miramo check_rent_control_perimeter .vscode/mcp.json
- Zed Miramo check_rent_control_perimeter ~/.config/zed/settings.json
- Windsurf Miramo check_rent_control_perimeter ~/.codeium/windsurf/mcp_config.json
- Cline Miramo check_rent_control_perimeter ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Miramo check_rent_control_perimeter ~/.gemini/settings.json
- Grok Miramo check_rent_control_perimeter .mcp.json (in your project root)
- ChatGPT Miramo check_rent_control_perimeter Settings → Connectors → Advanced → Developer mode
- Claude.ai Miramo check_rent_control_perimeter Settings → Connectors → Add custom connector
- LangChain Miramo check_rent_control_perimeter pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.miramo.fr/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 28 October 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.