Bucky is a remote MCP server that gives an AI agent 10 tools, among them explainFeasibilityStatus, getBuckyMcpGuide, getFeasibilitySnapshot. It answers at https://buckybuild.com/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 18 October 2026, succeeded.
Zoning, parcel, and development feasibility for a street address in Canada and the US.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
explainFeasibilityStatus | 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. Inputs: status, context |
getBuckyMcpGuide | 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 Inputs: context |
getFeasibilitySnapshot | 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 setb Inputs: address, source, context |
getProjectContext | Load one project with analysis envelope, compact agentStatus, document summaries, evidence summaries, and the project memory digest. Use before composing reports or after scheduling analysis. Inputs: projectId, documentsLimit, evidenceLimit, context |
produceProjectReport | 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 Inputs: projectId, audience, detail, request, preview, confirm |
runFeasibilityAnalysis | Enqueue a fresh deterministic analysis run for a saved project. Returns immediately with `agentStatus` (`queued`, `running`, `current`, `failed`, or `none`) and a receipt id; does not block on completion. Irreversible: a queued run cannot b Inputs: projectId, context |
saveToProject | Create a new project from a site (`create`), attach lots (`attach_parcels`, using lot.parcelExternalId from getFeasibilitySnapshot), or attach a knowledge reference (`attach_reference`). Pass lat and lng on `create`: they resolve the projec Inputs: action, name, address, lat, lng, projectId |
submitBuckyFeedback | 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 Inputs: submissionId, affectedToolName, context |
uiGetAnalysisStatus | Return only the analysis `agentStatus` for a project. Cheap enough to poll. Used by the Bucky app view; the model should call getProjectContext instead. Inputs: projectId, context |
updateProject | Patch project metadata (name, lifecycle status). 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. Inputs: projectId, name, lifecycleStatus, preview, undoOperationId, context |
Every block below points at https://buckybuild.com/api/mcp. Pick your client and copy.
claude mcp add --transport http bucky https://buckybuild.com/api/mcp
{
"mcpServers": {
"bucky": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://buckybuild.com/api/mcp"]
}
}
}{
"mcpServers": {
"bucky": {
"url": "https://buckybuild.com/api/mcp"
}
}
}{
"servers": {
"bucky": {
"type": "http",
"url": "https://buckybuild.com/api/mcp"
}
}
}{
"context_servers": {
"bucky": {
"url": "https://buckybuild.com/api/mcp"
}
}
}{
"mcpServers": {
"bucky": {
"serverUrl": "https://buckybuild.com/api/mcp"
}
}
}{
"mcpServers": {
"bucky": {
"url": "https://buckybuild.com/api/mcp"
}
}
}name: Bucky
version: 0.0.1
schema: v1
mcpServers:
- name: Bucky
type: streamable-http
url: https://buckybuild.com/api/mcp{
"mcpServers": {
"bucky": {
"httpUrl": "https://buckybuild.com/api/mcp"
}
}
}{
"mcpServers": {
"bucky": {
"type": "http",
"url": "https://buckybuild.com/api/mcp"
}
}
}{
"mcpServers": {
"bucky": {
"url": "https://buckybuild.com/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fbuckybuild.com%2Fapi%2Fmcp&type=streamable_http&id=bucky&name=Bucky
It answered our last check on 18 October 2026 in 282 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by buckybuild.com and served from buckybuild.com, the vendor's own domain: https://buckybuild.com/api/mcp.
10, as returned by the server's own tools/list on 10 September 2026: explainFeasibilityStatus, getBuckyMcpGuide, getFeasibilitySnapshot, getProjectContext, produceProjectReport, runFeasibilityAnalysis, saveToProject, submitBuckyFeedback, and 2 more.
It answered our last check on 18 October 2026 in 282 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://buckybuild.com/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.buckybuild. Endpoint host: buckybuild.com. ARD identifier: urn:air:com.buckybuild:mcp:bucky.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.