bim.house — words become buildings. Generate BIM, check code & structure, quote materials.
- Remote endpoint
Uptime
Checked · every day
99.88%from 13 days of checks
Up without downtime on 10 of 12 days with data; down 20 minutes in all, the longest 10 minutes on 5 November.
- No downtime
- Degraded
- Down over 5 minutes
- No data
- Not checked yet
Response time
Median 1631 ms, slowest 5% 20300 ms for the handshake and the tool list, over 30 days.
How far each check got
- Reached the address 72.2%
- Completed the handshake 72.2%
- Listed its tools 72.2%
19 tools at the last answer; the list changed on 11 Nov.
Every day
| Day | Result | Checks | Median |
|---|---|---|---|
| 12 Nov (today) | No verdict yet | 0 | – |
| 11 Nov | Down 10 minutes | 3of 1 | 1261 ms |
| 10 Nov | Slow answers | 1of 1 | 12431 ms |
| 9 Nov | Slow answers | 1of 1 | 15590 ms |
| 8 Nov | No downtime | 1of 1 | 3609 ms |
| 7 Nov | No downtime | 2of 1 | 4820 ms |
| 6 Nov | No downtime | 1of 1 | 2877 ms |
| 5 Nov | Down 10 minutes | 3of 1 | 1623 ms |
| 4 Nov | No downtime | 1of 1 | 1201 ms |
| 3 Nov | Slow answers | 1of 1 | 20300 ms |
| 2 Nov | No downtime | 1of 1 | 1295 ms |
| 1 Nov | No downtime | 1of 1 | 1229 ms |
| 31 Oct | No downtime | 2 | 1213 ms |
A failure counts as down time only when a second check five minutes later fails too. How we check
Connect to the publisher's own endpoint
Paste into Settings › Connectors › Add custom connector:
https://bim.house/mcp Run in a terminal:
claude mcp add --transport http bimhouse https://bim.house/mcp Add to ~/.cursor/mcp.json:
Add to ~/.config/devin/mcp_config.json:
Add to mcp.json (Program › Install › Edit mcp.json):
Add to config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows):
Add to ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project):
Add to ~/.config/eca/config.json (global) or .eca/config.json in the project:
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
{
"mcpServers": {
"bimhouse": {
"url": "https://bim.house/mcp"
}
}
} Add to .vscode/mcp.json:
{
"servers": {
"bimhouse": {
"type": "http",
"url": "https://bim.house/mcp"
}
}
} Add to ~/.config/zed/settings.json:
{
"context_servers": {
"bimhouse": {
"url": "https://bim.house/mcp"
}
}
} Add to cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
{
"mcpServers": {
"bimhouse": {
"type": "streamableHttp",
"url": "https://bim.house/mcp"
}
}
} Add to ~/.continue/config.yaml:
mcpServers:
- name: "bimhouse"
type: streamable-http
url: "https://bim.house/mcp" Add to ~/.config/goose/config.yaml:
extensions:
"bimhouse":
type: streamable_http
name: "bimhouse"
enabled: true
uri: "https://bim.house/mcp"
headers: {}
env_keys: []
envs: {}
timeout: 300 Add to ~/.gemini/settings.json:
{
"mcpServers": {
"bimhouse": {
"httpUrl": "https://bim.house/mcp"
}
}
} Add to ~/.llm/config.json:
Add to resources/assets/config/mcp.json in the installed app:
Add to ~/.boltai/mcp.json:
{
"mcpServers": {
"bimhouse": {
"url": "https://bim.house/mcp"
}
}
} This server's endpoint speaks streamable HTTP, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/agenvoy/mcp.json:
{
"servers": {
"bimhouse": {
"url": "https://bim.house/mcp"
}
}
} Add to ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
{
"amp.mcpServers": {
"bimhouse": {
"url": "https://bim.house/mcp"
}
}
} Add to anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:
{
"mcpServers": {
"bimhouse": {
"type": "streamable",
"url": "https://bim.house/mcp"
}
}
} Add to Augment Settings Panel – MCP section – Import from JSON (VS Code extension):
{
"mcpServers": {
"bimhouse": {
"type": "http",
"url": "https://bim.house/mcp"
}
}
} For agents: the install prompt
Every step above as one Markdown text, for an assistant installing it for you.
# Install the MCP server `house.bim/bimhouse`
Its page: https://plug.directory/servers/house.bim/bimhouse
It runs on the publisher's servers; the client connects to its URL.
Use the section for the person's client.
## Claude Desktop
Paste into Settings › Connectors › Add custom connector:
```text
https://bim.house/mcp
```
## Claude Code
Run in a terminal:
```sh
claude mcp add --transport http bimhouse https://bim.house/mcp
```
## Cursor, Devin Desktop, LM Studio, oterm, Bob Shell, ECA, Kiro, Kiro CLI
Merge into the place for the person's client:
- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- Bob Shell: ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
- Kiro: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)
- Kiro CLI: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)
```json
{
"mcpServers": {
"bimhouse": {
"url": "https://bim.house/mcp"
}
}
}
```
## VS Code
Merge into .vscode/mcp.json:
```json
{
"servers": {
"bimhouse": {
"type": "http",
"url": "https://bim.house/mcp"
}
}
}
```
## Zed
Merge into ~/.config/zed/settings.json:
```json
{
"context_servers": {
"bimhouse": {
"url": "https://bim.house/mcp"
}
}
}
```
## Cline
Merge into cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
```json
{
"mcpServers": {
"bimhouse": {
"type": "streamableHttp",
"url": "https://bim.house/mcp"
}
}
}
```
## Continue
Merge into ~/.continue/config.yaml:
```yaml
mcpServers:
- name: "bimhouse"
type: streamable-http
url: "https://bim.house/mcp"
```
## Goose
Merge into ~/.config/goose/config.yaml:
```yaml
extensions:
"bimhouse":
type: streamable_http
name: "bimhouse"
enabled: true
uri: "https://bim.house/mcp"
headers: {}
env_keys: []
envs: {}
timeout: 300
```
## Gemini CLI
Merge into ~/.gemini/settings.json:
```json
{
"mcpServers": {
"bimhouse": {
"httpUrl": "https://bim.house/mcp"
}
}
}
```
## Codex
Run in a terminal:
```sh
codex mcp add bimhouse --url https://bim.house/mcp
```
## mcp-client-cli, TUUI, BoltAI
This server's endpoint speaks streamable HTTP, which this client's documentation does not list among its transports; use another client for it.
## Agenvoy
Merge into ~/.config/agenvoy/mcp.json:
```json
{
"servers": {
"bimhouse": {
"url": "https://bim.house/mcp"
}
}
}
```
## Amp
Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
```json
{
"amp.mcpServers": {
"bimhouse": {
"url": "https://bim.house/mcp"
}
}
}
```
## AnythingLLM
Merge into anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:
```json
{
"mcpServers": {
"bimhouse": {
"type": "streamable",
"url": "https://bim.house/mcp"
}
}
}
```
## Augment Code
Merge into Augment Settings Panel – MCP section – Import from JSON (VS Code extension):
```json
{
"mcpServers": {
"bimhouse": {
"type": "http",
"url": "https://bim.house/mcp"
}
}
}
```
Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.
From the publisher's entry in the Official MCP Registry (the registry entry). Report a problem