# ProjectPermit (remote · projectpermit-mcp-production.up.railway.app)

Building permit requirements MCP for contractors and AI agents across 7 Canadian municipalities.

- Trust score: 23/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `projectpermit-mcp-production.up.railway.app`: 23/100 (this document), [markdown](https://verifymcp.io/servers/changhuliu-projectpermit/projectpermit-mcp-production.md), [page](https://verifymcp.io/servers/changhuliu-projectpermit/projectpermit-mcp-production)

## Channel facts

- Endpoint: `https://projectpermit-mcp-production.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.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-09-24.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 404.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

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

ProjectPermit is a hosted endpoint at https://projectpermit-mcp-production.up.railway.app/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 changhuliu-projectpermit 'https://projectpermit-mcp-production.up.railway.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "changhuliu-projectpermit": {
      "url": "https://projectpermit-mcp-production.up.railway.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "changhuliu-projectpermit": {
      "type": "http",
      "url": "https://projectpermit-mcp-production.up.railway.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.changhuliu-projectpermit]
url = "https://projectpermit-mcp-production.up.railway.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "changhuliu-projectpermit": {
      "type": "remote",
      "url": "https://projectpermit-mcp-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add changhuliu-projectpermit --url 'https://projectpermit-mcp-production.up.railway.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  changhuliu-projectpermit:
    url: "https://projectpermit-mcp-production.up.railway.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "changhuliu-projectpermit": {
      "Transport": "http",
      "Url": "https://projectpermit-mcp-production.up.railway.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add changhuliu-projectpermit -t streamable-http -u 'https://projectpermit-mcp-production.up.railway.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "changhuliu-projectpermit": {
      "type": "http",
      "url": "https://projectpermit-mcp-production.up.railway.app/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-09-04 (score 23, −42)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.23 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-01 (score 65, +1)

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

### 2026-08-30 (score 64, +2)

- [security] Tool “check_project_requirements” rewrote its description, which is the text the model reads
- [security] Tool “check_project_requirements_batch” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 140 → 181
- [functional improvement] Tool coverage: 0% → 71%
- [cosmetic] “check_project_requirements” reworded the description of “address”
- [cosmetic] “check_project_requirements” reworded the description of “context”
- [cosmetic] “check_project_requirements” reworded the description of “jurisdiction”
- [cosmetic] “check_project_requirements” reworded the description of “property”
- [cosmetic] “check_project_requirements” reworded the description of “resolve_address”

### 2026-08-29 (score 62, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “check_project_requirements” rewrote its description, which is the text the model reads
- [security] Tool “projectpermit_info” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional] New tool “check_project_requirements_batch”

### 2026-08-28 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-27 (score 61)

First indexed and scored.

## MCP tools (3)

### `projectpermit_info` (~40 tokens)

Use first to get supported Canadian cities/families, identity/idempotency and safe-writeback semantics. Capability discovery only; no permit determination is performed.

### `check_project_requirements` (~204 tokens)

Use for proposed work before quoting/scheduling. Start project with family + action and add only known facts. Returns evidence-linked determination, workflow/action bundle, deterministic identity, duplicate-suppression idempotency and mutation gate. Pass context.prior_decision_identity for repeat checks.

Input parameters:

- `address`: Optional civic address. Supply it with resolve_address=true only where ProjectPermit has a municipal address/GIS resolver.
- `context`: Optional workflow/idempotency context. Preserve unknown facts rather than guessing them.
- `jurisdiction` (string, required): Municipality id. Supported now: gatineau_qc, ottawa_on, toronto_on, mississauga_on, laval_qc, longueuil_qc, vancouver_bc.
- `project` (required)
- `property`: Known property/overlay facts. Resolver-specific fields are also accepted.
- `resolve_address` (boolean): When true, enrich known property facts from first-party municipal address/GIS data before deterministic rule evaluation.

### `check_project_requirements_batch` (~56 tokens)

Evaluate 1-50 normalized projects in one call. Each item exposes jurisdiction, project.family/action, optional property/address/context and client_ref. Malformed items remain isolated as per-item failures.

Input parameters:

- `items` (array, required)

## Diagnostics

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

## Score history

- 2026-09-24: 23
- 2026-09-23: 23
- 2026-09-22: 23
- 2026-09-21: 23
- 2026-09-20: 23
- 2026-09-19: 23
- 2026-09-18: 23
- 2026-09-17: 23
- 2026-09-16: 23
- 2026-09-15: 23
- 2026-09-14: 23
- 2026-09-13: 23
- 2026-09-12: 23
- 2026-09-11: 23
- 2026-09-10: 23
- 2026-09-09: 23
- 2026-09-08: 23
- 2026-09-07: 23
- 2026-09-06: 23
- 2026-09-05: 23
- 2026-09-04: 23
- 2026-09-03: 65
- 2026-09-02: 65
- 2026-09-01: 65
- 2026-08-31: 64
- 2026-08-30: 64
- 2026-08-29: 62
- 2026-08-28: 61
- 2026-08-27: 61

## Common questions

### What is the ProjectPermit MCP server?

ProjectPermit is an MCP server listed in the public MCP registry as io.github.ChanghuLiu/projectpermit. Building permit requirements MCP for contractors and AI agents across 7 Canadian municipalities. This page covers its hosted endpoint (https://projectpermit-mcp-production.up.railway.app/mcp).

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

ProjectPermit scores 23 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 ProjectPermit MCP server expose?

ProjectPermit exposes 3 tools: projectpermit_info, check_project_requirements, check_project_requirements_batch. Their descriptions and schemas cost roughly 300 tokens of context every time the server is loaded.

### Does the ProjectPermit MCP server require authentication?

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

### Is the ProjectPermit MCP server still maintained?

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

## Links

- Remote endpoint: https://projectpermit-mcp-production.up.railway.app/mcp
- Repository: https://github.com/ChanghuLiu/projectpermit-mcp
- Website: https://projectpermit-api-v2-production.up.railway.app/
- Changelog RSS feed: https://verifymcp.io/servers/changhuliu-projectpermit/projectpermit-mcp-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/changhuliu-projectpermit/projectpermit-mcp-production.json
- HTML version of this page: https://verifymcp.io/servers/changhuliu-projectpermit/projectpermit-mcp-production