# Matchoffice MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.matchoffice%2Fmcp
Registry id: `mcp-registry/com.matchoffice/mcp`
Status: live (checked 2026-10-27T01:43:34.694Z)

## Verdict

Matchoffice MCP server answered 99.61% of Glimind's liveness checks over 30 days, better than 18% of MCP servers, with 2436 ms median handshake and 4 outages in 90 days. Its agent-readiness grade is A (94/100) across 3 tools, costing an agent about 1,473 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.61% | 18% of MCP servers |
| Median handshake latency | 2436 ms | 2% of MCP servers |
| p95 handshake latency | 4257 ms | — |
| Checks in 30 days | 2,339 | — |
| Outages, 90 days | 4 | — |
| Median recovery | 13.3 h | — |
| Agent-readiness score | 94/100 (A) | 78% of MCP servers |
| Tools | 3 | — |
| Tool-list size for an agent | ~1,473 tokens | 59% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "matchoffice-mcp-server": {
      "type": "http",
      "url": "https://www.matchoffice.com/api/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http matchoffice-mcp-server https://www.matchoffice.com/api/mcp
```

## Tools (3)

- `create_order`: Submit an inquiry for a location
- `get_location`: Get full details for a single location by ID
- `search_locations`: Search for available commercial real estate locations

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.