BuyNearby
REMOTE · BUYNEARBY.STORE
Shop BuyNearby's local Calgary marketplace, book couriers, and request personal shopping runs.
Available components
Last scanned (14 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
Recent critical change
Authorization (13 Nov 2026). See the changelog before you install this server.
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (place_order). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1001 tokens (~125/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management92
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 0 breaking changes, 1 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 48% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 13 Nov 26 −13
- Authorization: pass → fail ▼ critical
- Stability: pass → fail ▼ security
- Tool “book_courier” rewrote its description, which is the text the model reads security
- Tool “check_stock” rewrote its description, which is the text the model reads security
- Tool “get_stores” rewrote its description, which is the text the model reads security
- Tool “get_todays_deals” rewrote its description, which is the text the model reads security
- Tool “place_cart_order” rewrote its description, which is the text the model reads security
- Tool “place_order” rewrote its description, which is the text the model reads security
- Tool “search_products” rewrote its description, which is the text the model reads security
- Tool “shop_and_deliver” rewrote its description, which is the text the model reads security
- Tool “book_courier” is now declared destructive security
- Tool “place_cart_order” is now declared destructive security
- Tool “place_order” is now declared destructive security
- Tool “shop_and_deliver” is now declared destructive security
- Schema quality: 179 → 125 ▲ functional
- “get_stores” dropped the optional parameter “city” cosmetic
- “search_products” dropped the optional parameter “city” cosmetic
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 8 Nov 26 0
- Stability: 0.97 → pass security
- 7 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Oct 26 0
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- HTTPS: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 28 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- HTTPS: pass → fail ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://buynearby.store/api/v1/mcp-server.php
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cpcontacts.buynearby.store | CN=YR2,O=Let's Encrypt,C=US | 9 Nov 2026 | 7 Feb 2027 | RSA 2048 | SHA256-RSA | 69aeba2bd3b1935bdaf6fcbfde4fd94e0b1 |
| SANs: autodiscover.buynearby.store, buynearby.store, cpanel.buynearby.store, cpcalendars.buynearby.store, cpcontacts.buynearby.store, mail.buynearby.store, webdisk.buynearby.store, webmail.buynearby.store, www.buynearby.store | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of buynearby.store. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| store. | DS published | 2327 | 13 | Verified |
| buynearby.store. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(self), microphone=(self), geolocation=(self), payment=(self), usb=(self), serial=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://buynearby.store/api/v1/mcp-server.php | Verified | 200 | |
| http (plaintext) | http://buynearby.store/api/v1/mcp-server.php | HTTPS enforced | 301 | https://buynearby.store/api/v1/mcp-server.php |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
book_courier ~355
Gets a quote for, books, checks the status of, or cancels a point-to-point courier delivery in Calgary. A booking is real and a driver is assigned when available; payment is a link sent to the customer by text and this call never charges a card. A booking can be cancelled while it is pending or assigned.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| booking_ref | string | – | Required for action 'status'/'cancel', e.g. 'CB-20260912-0007' |
| cancel_reason | string | – | Optional, action 'cancel' only |
| customer_email | string | – | – |
| customer_name | string | – | Required for action 'book' |
| customer_phone | string | – | Required for action 'book', 'status', and 'cancel' — for 'status'/'cancel' this must match the phone on the booking (it's the ownership check, since booking_ref alone is guessable) |
| delivery_address | string | – | Required for action 'quote'/'book' |
| delivery_notes | string | – | – |
| idempotency_key | string | – | Optional, action 'book' only — pass the same value on a retry (e.g. after a dropped connection) to avoid creating a duplicate booking |
| package_count | integer | – | – |
| pickup_address | string | – | Required for action 'quote'/'book' |
| preferred_dropoff_time | string | – | Any parseable date/time the customer needs the delivery completed by, e.g. 'today 10pm'; must not be before preferred_pickup_time |
| preferred_pickup_time | string | – | Any parseable date/time; omit for ASAP dispatch |
| size_tier | string | – | – |
No output schema declared.
No examples provided.
check_stock ~48
Returns the live stock level of one product, optionally for a single store.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | string | yes | Product ID from search results |
| store_id | integer | – | Store ID (optional) |
No output schema declared.
No examples provided.
get_stores ~18
Returns local Calgary stores with their location information.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_todays_deals ~70
Returns today's discounted products and active flash deals at local stores, with sale and regular prices.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results per section. Default 20, max 50 |
| store_id | integer | – | Limit to one store (optional — omit for deals across all stores) |
No output schema declared.
No examples provided.
place_cart_order ~162
Places one order for several products from one or more BuyNearby stores. Prices and stock come from the live catalog. Creates a real order; the customer receives a payment link by text or email, the card is held and is only charged after the store confirms the order. Delivery or pickup.
| Name | Type | Req | Description |
|---|---|---|---|
| coupon_code | string | – | – |
| customer_email | string | – | – |
| customer_name | string | yes | – |
| customer_phone | string | yes | – |
| delivery_address | string | yes | Required unless fulfillment_type is 'pickup' |
| express | boolean | – | – |
| fulfillment_type | string | – | – |
| items | array | yes | – |
| tip_percentage | number | – | Only set this if the user explicitly chose a tip - don't default one in on their behalf |
No output schema declared.
No examples provided.
place_order ~155
Places an order for one product from a BuyNearby store. Creates a real order; the customer receives a payment link by text or email, the card is held and is only charged after the store confirms the order. Guests provide name, phone and email; signed-in customers' saved details are used.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_email | string | yes | – |
| delivery_address | string | yes | – |
| express | boolean | – | Adds an express fee (default $4.99 CAD) |
| product_id | string | yes | – |
| quantity | integer | – | – |
| requested_by_time | string | – | Any parseable date/time, e.g. 'today 22:00' - recorded on the order, not an enforced SLA at this tier |
No output schema declared.
No examples provided.
search_products ~67
Searches products available at local Calgary stores. Returns product name, store, price, stock level and store categories.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of results (max 50) |
| q | string | yes | Product search query — can be a product name, ingredient, or natural language description |
No output schema declared.
No examples provided.
shop_and_deliver ~126
Books a personal shopping run: a BuyNearby driver shops the given item list at a named store and delivers it. Creates a real order; the customer is charged the driver's actual receipt total afterward. Item prices given are estimates.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_email | string | – | – |
| customer_name | string | yes | – |
| customer_phone | string | yes | – |
| delivery_address | string | yes | – |
| items | array | yes | – |
| notes | string | – | – |
| store_hint | string | yes | Physical store name, e.g. 'Purdys Chocolatier Chinook Centre' |
No output schema declared.
No examples provided.
How do I install the BuyNearby MCP server?
BuyNearby is a hosted endpoint at https://buynearby.store/api/v1/mcp-server.php, 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.
remote · buynearby.store
claude mcp add --transport http store-buynearby-mcp 'https://buynearby.store/api/v1/mcp-server.php'
What is the BuyNearby MCP server?
BuyNearby is an MCP server listed in the public MCP registry as store.buynearby/mcp. Shop BuyNearby's local Calgary marketplace, book couriers, and request personal shopping runs. This page covers its hosted endpoint (https://buynearby.store/api/v1/mcp-server.php).
Is the BuyNearby MCP server safe to use?
BuyNearby scores 75 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 BuyNearby MCP server expose?
BuyNearby exposes 8 tools: search_products, check_stock, get_todays_deals, get_stores, place_order, and 3 more. Their descriptions and schemas cost roughly 1,001 tokens of context every time the server is loaded.
Does the BuyNearby MCP server require authentication?
No. We connected to BuyNearby without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BuyNearby MCP server still maintained?
BuyNearby is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the BuyNearby MCP server?
VerifyMCP ran 13 checks on BuyNearby, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.