Is com.buckybuild/bucky up? Live MCP status
Yes, it is up. It answered an MCP server/discover with no credential and negotiated protocol 2026-07-28.
A stock client connected with no credential and negotiated 2026-07-28. Use it.
| Outcome | usable |
|---|---|
| HTTP status | 200 |
| Protocol version | 2026-07-28 |
| Server says it is | bucky 1.0.1 |
| Answered in | 118 ms |
| Endpoint checked | https://buckybuild.com/api/mcp |
| Checked |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Published, does not validate: an A2A 0.3 card: no `supportedInterfaces`, which 1.0 requires in place of `url` and `protocolVersion`. A2A 0.3 shape; 1 skill; JSONRPC./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 200 with an HTML page, not JSON).https://buckybuild.com/api/mcp/server-card |
| MCP server card (SEP-1649 location) | Published, does not validate: `authentication` needs `required` and `schemes`. SEP-1649 shape; bucky 1.0.1; MCP 2026-07-28; streamable-http./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://buckybuild.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 15 tools: cityInventory, explainFeasibilityStatus, getBuckyMcpGuide, getBylawSection, getFeasibilitySnapshot, getProjectContext, previewSiteCoverage, produceProjectReport, runFeasibilityAnalysis, saveToProject, screenLots, setProjectMapListing, submitBuckyFeedback, uiGetAnalysisStatus, updateProject.
Its tools changed between 2026-09 and 2026-10:
- Added (5):
cityInventory,getBylawSection,previewSiteCoverage,screenLots,setProjectMapListing explainFeasibilityStatus: description, input schema changedgetBuckyMcpGuide: description, input schema changedgetFeasibilitySnapshot: description, input schema changedgetProjectContext: description, input schema changedproduceProjectReport: description, input schema changedrunFeasibilityAnalysis: description, input schema changedsaveToProject: description, input schema changedsubmitBuckyFeedback: input schema changeduiGetAnalysisStatus: input schema changedupdateProject: description, input schema changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | com.buckybuild/bucky |
|---|---|
| Title | Bucky |
| Description | Zoning, parcel, and development feasibility for a street address in Canada and the US. |
| Endpoint | https://buckybuild.com/api/mcp |
| Publisher repository | https://github.com/markbucky/bucky-plugin |
| Version | 1.0.1 |
| Listing updated |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt