# Bucky (remote · buckybuild.com)

Zoning, parcel, and development feasibility for a street address in Canada and the US.

- Trust score: 84/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `buckybuild.com`: 84/100 (this document), [markdown](https://verifymcp.io/servers/com-buckybuild-bucky/api-mcp.md), [page](https://verifymcp.io/servers/com-buckybuild-bucky/api-mcp)

## Channel facts

- Endpoint: `https://buckybuild.com/api/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-09-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 73/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3845 tokens (~295/item across 13 items; 11 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 79% 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

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

Bucky is a hosted endpoint at https://buckybuild.com/api/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 com-buckybuild-bucky 'https://buckybuild.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-buckybuild-bucky": {
      "url": "https://buckybuild.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-buckybuild-bucky": {
      "type": "http",
      "url": "https://buckybuild.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-buckybuild-bucky]
url = "https://buckybuild.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-buckybuild-bucky": {
      "type": "remote",
      "url": "https://buckybuild.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-buckybuild-bucky --url 'https://buckybuild.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-buckybuild-bucky:
    url: "https://buckybuild.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-buckybuild-bucky": {
      "Transport": "http",
      "Url": "https://buckybuild.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-buckybuild-bucky -t streamable-http -u 'https://buckybuild.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-buckybuild-bucky": {
      "type": "http",
      "url": "https://buckybuild.com/api/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-21 (score 84, +1)

- [security] Resource “Bucky” now points somewhere else: ui://bucky/app.html → ui://bucky/app.html?v=48a465c08e93
- [security] Tool “getProjectContext” rewrote its description, which is the text the model reads
- [security] Tool “produceProjectReport” rewrote its description, which is the text the model reads
- [security] Tool “runFeasibilityAnalysis” rewrote its description, which is the text the model reads
- [security] Tool “saveToProject” rewrote its description, which is the text the model reads
- [security] Tool “setProjectMapListing” rewrote its description, which is the text the model reads
- [security] Tool “updateProject” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 257 → 295
- [functional improvement] Tool coverage: 68% → 79%
- [functional] Schema quality: excellent → good
- [cosmetic] “getProjectContext” added an optional parameter “project”
- [cosmetic] “produceProjectReport” added an optional parameter “project”
- [cosmetic] “runFeasibilityAnalysis” added an optional parameter “project”
- [cosmetic] “saveToProject” added an optional parameter “project”
- [cosmetic] “setProjectMapListing” added an optional parameter “project”
- [cosmetic] “updateProject” added an optional parameter “project”
- [cosmetic] “explainFeasibilityStatus” reworded the description of “status”
- [cosmetic] “getProjectContext” reworded the description of “projectId”
- [cosmetic] “produceProjectReport” reworded the description of “projectId”
- [cosmetic] “runFeasibilityAnalysis” reworded the description of “projectId”
- [cosmetic] “saveToProject” reworded the description of “projectId”
- [cosmetic] “setProjectMapListing” reworded the description of “projectId”
- [cosmetic] “updateProject” reworded the description of “projectId”
- [cosmetic] “produceProjectReport” made “projectId” optional
- [cosmetic] “runFeasibilityAnalysis” made “projectId” optional
- [cosmetic] “setProjectMapListing” made “projectId” optional
- [cosmetic] “updateProject” made “projectId” optional

### 2026-09-19 (score 83, +1)

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

### 2026-09-17 (score 82, +1)

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

### 2026-09-16 (score 81, 0)

- [security] Tool “explainFeasibilityStatus” rewrote its description, which is the text the model reads
- [security] Tool “getFeasibilitySnapshot” rewrote its description, which is the text the model reads
- [security] Tool “getProjectContext” rewrote its description, which is the text the model reads
- [security] Tool “saveToProject” rewrote its description, which is the text the model reads
- [security] Tool “updateProject” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 212 → 257
- [functional improvement] Tool coverage: 59% → 68%
- [functional] Schema quality: good → excellent
- [functional] New tool “setProjectMapListing”
- [cosmetic] “saveToProject” added an optional parameter “externalRef”
- [cosmetic] “updateProject” added an optional parameter “externalRef”
- [cosmetic] “explainFeasibilityStatus” reworded the description of “status”
- [cosmetic] “saveToProject” reworded the description of “address”
- [cosmetic] “saveToProject” reworded the description of “lat”
- [cosmetic] “saveToProject” reworded the description of “lng”
- [cosmetic] “submitBuckyFeedback” reworded the description of “submissionId”
- [cosmetic] “submitBuckyFeedback” made “submissionId” optional

### 2026-09-15 (score 81, +1)

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

### 2026-09-13 (score 80, +1)

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

### 2026-09-11 (score 79, +1)

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

### 2026-09-08 (score 78, +1)

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

## MCP tools (11)

### `getBuckyMcpGuide` (~179 tokens)

Get the Bucky MCP guide

Return a static guide to the Bucky MCP surface: what works without sign-in, how to start OAuth by calling a gated tool, how to connect Cursor or the CLI with a real account, and feasibility safety rules. Makes no database, geocoding, AI, or third-party API call.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…

### `explainFeasibilityStatus` (~341 tokens)

Explain a Bucky feasibility status

Explain one Bucky coverage or per-fact provenance status and the safe next action. This is a pure static lookup: it does not inspect an address, retrieve property data, or call a database, geocoder, AI model, or third-party API. Accepts exactly one of: live, live_unavailable, planned_not_live, geo_division_uncatalogued, unseeded_place, geocode_failed, cited, cited_conditional, conditional_unresolved, no_limit_in_bylaw, not_extracted, site_specific_schedule, unverified_default.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `status` (string, required): A Bucky coverage resolution status or per-fact provenance status returned by a feasibility result. Must be copied verbatim from a feasibility result — one of: live, live_unavailable, planned_not_live…

### `getFeasibilitySnapshot` (~391 tokens)

Get feasibility snapshot for an address

Look up what can be built at a specific street address in Canada or the US. Returns the lot (area, width, depth), its zone and permitted uses, and the building envelope (height, storeys, site coverage, FSR, and front/rear/side/flanking setbacks) in one call. Use when someone asks what they can build, how tall, how close to the property line, how big their lot is, or what their property is zoned for. Do not use for questions that are not about a specific address — it resolves one address at a time and cannot search or compare. Every envelope value carries a `status`. A null value with status `no_limit_in_bylaw` means the bylaw sets no limit; a null value with status `not_extracted` means the value is unknown to Bucky; a null value with status `site_specific_schedule` means the zone is governed by a per-site schedule, not a zone table. Never report `not_extracted` or `site_specific_schedule` as "no limit" or as zero.

Input parameters:

- `address` (string, required): Street address to analyse, e.g. "4170 Sophia St, Vancouver BC".
- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `source` (string, required): Which question the caller is answering. Used for attribution and to pick the link back; the payload is the same either way.

### `runFeasibilityAnalysis` (~299 tokens)

Run project feasibility analysis

Enqueue a fresh deterministic analysis run for a saved project. Pass `projectId`, or `project` with the name the user said; with neither, the result lists their projects and nothing is queued. Returns immediately with `agentStatus` (`queued`, `running`, `current`, `failed`, or `none`) and a receipt id; does not block on completion. Irreversible: a queued run cannot be un-queued from MCP. Re-check with `getProjectContext`, but no more than once every 15 seconds — it is a multi-query bundle, not a status endpoint.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `project` (string): Project name to match, when you do not have the UUID. Case-insensitive; an exact name wins over a partial one. Matching more than one lists the candidates instead of guessing.
- `projectId` (string): Project UUID. Omit if you pass `project`.

### `getProjectContext` (~268 tokens)

Get project context bundle

Load one project with analysis envelope, compact agentStatus, document summaries, evidence summaries, the project memory digest, and external_ref when the project was imported from another system. You do not need a UUID: pass `project` with the name the user said, or call with neither and the result lists their projects to choose from. Use before composing reports or after scheduling analysis.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `documentsLimit` (integer, required)
- `evidenceLimit` (integer, required)
- `project` (string): Project name to match, when you do not have the UUID. Case-insensitive; an exact name wins over a partial one. Matching more than one lists the candidates instead of guessing.
- `projectId` (string): Project UUID. Omit if you pass `project`.

### `saveToProject` (~747 tokens)

Create or attach to a project

Create a new project from a site (`create`), attach lots (`attach_parcels`, using lot.parcelExternalId from getFeasibilitySnapshot), or attach a knowledge reference (`attach_reference`). On `create`, pass `address`, or `lat` and `lng` from getFeasibilitySnapshot when you already have them: coordinates resolve the project to a city, and an address alone is geocoded server-side. Check `geography` on the result — `resolved: false` means the project has no city context and feasibility analysis will have nothing to resolve against, and `coordinateSource: "geocoded"` means the server picked the point, so confirm it is the right site. preview=true returns the field-level diff and writes nothing. A write returns a receipt. Not reversible on this surface: MCP cannot archive a project, detach a parcel, or detach a reference. attach_parcels and attach_reference take `projectId`, or `project` with the name the user said; with neither, the result lists their projects and nothing is attached. Create accepts idempotencyKey and externalRef (`<system>:<id>`, e.g. `notion:<page-id>`) so an imported project can be looked up later.

Input parameters:

- `action` (string, required): create: new project from a site. attach_parcels: attach lots to an existing project (use lot.parcelExternalId from getFeasibilitySnapshot). attach_reference: link a knowledge section to an existing p…
- `address` (string): Street address of the site. On `create` this is geocoded server-side when lat/lng are not supplied, and is what gets recorded as the project address.
- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `externalRef` (string): Provenance of an imported project. Canonical form is `<system>:<id>` (e.g. `notion:<page-id>`). Unique per creator when set. Returned on getProjectContext. Distinct from idempotencyKey.
- `idempotencyKey` (string)
- `lat` (number): Latitude from getFeasibilitySnapshot. Supplied coordinates are never re-geocoded.
- `lng` (number): Longitude from getFeasibilitySnapshot.
- `name` (string)
- `parcelExternalIds` (array): Source parcel ids to attach. Copy lot.parcelExternalId from getFeasibilitySnapshot, or from bucky parcels search.
- `preview` (boolean, required): When true, return the field-level diff and write nothing.
- `project` (string): Project name to match instead of a UUID, for attach_parcels and attach_reference. Matching more than one lists the candidates instead of guessing. Ignored by create.
- `projectId` (string): Existing project UUID. Required by attach_parcels and attach_reference unless you pass `project`; ignored by create.
- `radiusM` (integer): Search half-width in metres when resolving parcel ids. Default 150.
- `role` (string): build is the lot being developed; context is surrounding land. Default build.
- `sectionUuid` (string)

### `updateProject` (~372 tokens)

Update project fields

Patch project metadata (name, lifecycle status, externalRef). Pass `projectId`, or `project` with the name the user said; with neither, the result lists their projects and nothing is written. preview=true returns the field-level diff and writes nothing. A write returns a receipt; undoOperationId restores the captured prior fields. Does not archive or delete.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `externalRef`: Provenance of an imported project. Canonical form is `<system>:<id>` (e.g. `notion:<page-id>`). Unique per creator when set. Pass null to clear.
- `lifecycleStatus` (string)
- `name` (string)
- `preview` (boolean, required): When true, return the field-level diff and write nothing. Combined with undoOperationId, returns the stored receipt.
- `project` (string): Project name to match, when you do not have the UUID. Case-insensitive; an exact name wins over a partial one. Matching more than one lists the candidates instead of guessing.
- `projectId` (string): Project UUID. Omit if you pass `project`.
- `undoOperationId` (string): Receipt id from a prior updateProject write. Restores the captured prior fields. With preview=true, inspects the receipt instead.

### `setProjectMapListing` (~429 tokens)

List or unlist a project on the public map

Put a project on the public Bucky map, or take it off. Pass `projectId`, or `project` with the name the user said; with neither, the result lists their projects and nothing is published. Listing publishes the build-lot centroid, the project name, its zone category, typology and lifecycle status to anyone — signed in or not. Nothing else about the project is published. The project must have a build lot with a centroid; a project that has only an address and no attached build parcel cannot be pinned. Ask the human before listing a site that is not already public knowledge. A client, a friend, or a private residence is theirs to publish, not yours. preview=true returns the current state, the exact pin that would be published, and any privacy warning, and writes nothing. Unlisting removes the pin but does not un-share anything already collected while it was public.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `listed` (boolean, required): true lists the project on the public map; false removes it. Listing publishes the build-lot centroid and the project name to anyone, signed in or not.
- `preview` (boolean, required): When true, return the current listing state, the pin that would be published, and any privacy warning, and write nothing.
- `project` (string): Project name to match, when you do not have the UUID. Case-insensitive; an exact name wins over a partial one. Matching more than one lists the candidates instead of guessing.
- `projectId` (string): Project UUID. Omit if you pass `project`.

### `produceProjectReport` (~355 tokens)

Compose and export a project report PDF

Pass `projectId`, or `project` with the name the user said; with neither, the result lists their projects and no meter is spent. Compose a grounded report plan, optionally preview without spending export meter (`preview=true`), or confirm export (`confirm=true`) to save the plan and return a short-lived signed download URL plus a receipt — never PDF bytes in the tool result. Confirm spends `records.exports` and is irreversible.

Input parameters:

- `audience` (string, required)
- `confirm` (boolean, required): When true, compose (if needed), save, export PDF, and return a download URL. Required when preview is false. Spends records.exports and cannot be undone.
- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `detail` (string, required)
- `planName` (string)
- `preview` (boolean, required): When true, compose only — no export meter spend and no download URL.
- `project` (string): Project name to match, when you do not have the UUID. Case-insensitive; an exact name wins over a partial one. Matching more than one lists the candidates instead of guessing.
- `projectId` (string): Project UUID. Omit if you pass `project`.
- `request` (string)

### `submitBuckyFeedback` (~243 tokens)

Submit feedback to Bucky

Open a human-reviewed feedback form and submit it to the Bucky product team. Call only when the user explicitly asks to send feedback, report a problem, suggest an improvement, or praise something. The server asks the MCP client to show the form; nothing is saved unless the human accepts it. Do not use for silent agent self-reporting.

Input parameters:

- `affectedToolName` (string): Tool the user is commenting on, when already known
- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `submissionId` (string): Optional. A UUID for this submission; generated server-side when omitted. Pass the same UUID when retrying this exact feedback so it is not recorded twice.

### `uiGetAnalysisStatus` (~159 tokens)

Get analysis status

Return only the analysis `agentStatus` for a project. Cheap enough to poll. Used by the Bucky app view; the model should call getProjectContext instead.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `projectId` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-buckybuild-bucky/api-mcp#diagnostics

## Score history

- 2026-09-21: 84
- 2026-09-20: 83
- 2026-09-19: 83
- 2026-09-18: 82
- 2026-09-17: 82
- 2026-09-16: 81
- 2026-09-15: 81
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 78
- 2026-09-09: 78
- 2026-09-08: 78
- 2026-09-07: 77
- 2026-09-06: 77
- 2026-09-05: 76
- 2026-09-04: 76
- 2026-09-03: 75
- 2026-09-02: 75
- 2026-09-01: 74
- 2026-08-31: 74
- 2026-08-30: 74
- 2026-08-29: 73
- 2026-08-28: 73

## Common questions

### What is the Bucky MCP server?

Bucky is an MCP server listed in the public MCP registry as com.buckybuild/bucky. Zoning, parcel, and development feasibility for a street address in Canada and the US. This page covers its hosted endpoint (https://buckybuild.com/api/mcp).

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

Bucky scores 84 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 Bucky MCP server expose?

Bucky exposes 11 tools: getBuckyMcpGuide, explainFeasibilityStatus, getFeasibilitySnapshot, runFeasibilityAnalysis, getProjectContext, and 6 more. Their descriptions and schemas cost roughly 3,783 tokens of context every time the server is loaded.

### Does the Bucky MCP server require authentication?

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

### Is the Bucky MCP server still maintained?

Bucky is still listed as active in the MCP registry. We last reached this channel on 21 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://buckybuild.com/api/mcp
- Repository: https://github.com/markbucky/bucky-plugin
- Website: https://buckybuild.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-buckybuild-bucky/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-buckybuild-bucky/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-buckybuild-bucky/api-mcp