# BrickTable (remote · bricktable.co)

Tokenized real estate on RealT, Lofty, Binaryx and Reental: listings, executed trades and yields.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `bricktable.co`: 65/100 (this document), [markdown](https://verifymcp.io/servers/co-bricktable-bricktable/bricktable.md), [page](https://verifymcp.io/servers/co-bricktable-bricktable/bricktable)

## Channel facts

- Endpoint: `https://bricktable.co/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 852 tokens (~170/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the BrickTable MCP server?

BrickTable is a hosted endpoint at https://bricktable.co/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http co-bricktable-bricktable 'https://bricktable.co/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-bricktable-bricktable": {
      "url": "https://bricktable.co/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-bricktable-bricktable": {
      "type": "http",
      "url": "https://bricktable.co/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-bricktable-bricktable]
url = "https://bricktable.co/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-bricktable-bricktable": {
      "type": "remote",
      "url": "https://bricktable.co/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-bricktable-bricktable --url 'https://bricktable.co/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-bricktable-bricktable:
    url: "https://bricktable.co/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-bricktable-bricktable": {
      "Transport": "http",
      "Url": "https://bricktable.co/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-bricktable-bricktable -t streamable-http -u 'https://bricktable.co/mcp'
```

### Other

```json
{
  "mcpServers": {
    "co-bricktable-bricktable": {
      "type": "http",
      "url": "https://bricktable.co/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-19 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 64)

First indexed and scored.

## MCP tools (5)

### `search_properties` (~251 tokens)

Search tokenized properties

Find tokenized real-estate listings across RealT, Lofty, Binaryx and Reental. Filter by platform, country, text, payout status or recent trading. Each row has the last traded price, issue price, yield with its basis, payout status and caveats.

Input parameters:

- `country` (string): Country name, e.g. 'United States', 'Spain'. Case-insensitive.
- `include_exited` (boolean): Include sold/redeemed and unlisted listings. Default false.
- `limit` (integer): Default 20.
- `payout_status` (string): regular = distributions arriving on schedule; stalled = overdue; not_started = not yet paying (e.g. under construction).
- `platform` (string): Limit to one platform. Omit for all four.
- `query` (string): Text matched against the address/title and location, e.g. 'Detroit' or 'Chase St'.
- `sort` (string): Default last_trade (most recently traded first). 'yield' ranks listings whose distributions are being paid first, then those that are not, then off-plan projections.
- `traded_within_days` (integer): Only listings with an executed trade in this many days.

### `get_property` (~95 tokens)

Get one tokenized property

Full profile of one listing by its BrickTable id (from search_properties): price and issue price, yield with basis, payout status, tokens, holders and concentration, rent, ZIP-level home value and rent (US), recent trading, and caveats.

Input parameters:

- `id` (string, required): BrickTable property id, e.g. 'lofty-01JGMSZ4NEGCFF8T8CEE5XXYQ7'.

### `get_property_trades` (~158 tokens)

Executed trades for one property

Recorded secondary-market fills for one listing over the last 90 days, newest first, with quantity, price, settlement currency, USD value and a block-explorer link. Includes a summary (fill count, USD volume, volume-weighted price). The full history back to 2022 is available as a data license at bricktable.co/data.

Input parameters:

- `days` (integer): Look-back window, up to 90 days on the free server. Default 90.
- `limit` (integer): Max fills returned (newest first). Default 50. The summary covers the whole window.
- `property_id` (string, required): BrickTable property id from search_properties, e.g. 'realt-...' or 'lofty-...'.

### `get_recent_trades` (~53 tokens)

Latest trades across platforms

The most recent executed fills across all four platforms (or one), newest first.

Input parameters:

- `limit` (integer): Default 20.
- `platform` (string): Limit to one platform. Omit for all four.

### `get_platform_overview` (~63 tokens)

Platform overview

Per-platform summary: listing counts, how many are paying distributions, traded volume over 30 and 90 days, and the median last traded price as a share of issue price.

Input parameters:

- `platform` (string): Limit to one platform. Omit for all four.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-bricktable-bricktable/bricktable#diagnostics

## Score history

- 2026-11-21: 65
- 2026-11-20: 65
- 2026-11-19: 65
- 2026-11-18: 64
- 2026-11-17: 64

## Common questions

### What is the BrickTable MCP server?

BrickTable is an MCP server listed in the public MCP registry as co.bricktable/bricktable. Tokenized real estate on RealT, Lofty, Binaryx and Reental: listings, executed trades and yields. This page covers its hosted endpoint (https://bricktable.co/mcp).

### Is the BrickTable MCP server safe to use?

BrickTable scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the BrickTable MCP server expose?

BrickTable exposes 5 tools: search_properties, get_property, get_property_trades, get_recent_trades, get_platform_overview. Their descriptions and schemas cost roughly 620 tokens of context every time the server is loaded.

### Does the BrickTable MCP server require authentication?

No. We connected to BrickTable without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the BrickTable MCP server still maintained?

BrickTable is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the BrickTable MCP server?

VerifyMCP ran 12 checks on BrickTable, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about BrickTable: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://bricktable.co/mcp
- Website: https://bricktable.co/data
- Changelog RSS feed: https://verifymcp.io/servers/co-bricktable-bricktable/bricktable.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-bricktable-bricktable/bricktable/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/co-bricktable-bricktable/bricktable.json
- HTML version of this page: https://verifymcp.io/servers/co-bricktable-bricktable/bricktable
