BuyNearby
REMOTE · BUYNEARBY.STORE · SCANNED SEP 24
Shop BuyNearby's local Calgary marketplace, book couriers, and request personal shopping runs.
Available components
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1434 tokens (~179/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 Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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'
{
"mcpServers": {
"store-buynearby-mcp": {
"url": "https://buynearby.store/api/v1/mcp-server.php"
}
}
} {
"servers": {
"store-buynearby-mcp": {
"type": "http",
"url": "https://buynearby.store/api/v1/mcp-server.php"
}
}
} [mcp_servers.store-buynearby-mcp] url = "https://buynearby.store/api/v1/mcp-server.php"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"store-buynearby-mcp": {
"type": "remote",
"url": "https://buynearby.store/api/v1/mcp-server.php",
"enabled": true
}
}
} openclaw mcp add store-buynearby-mcp --url 'https://buynearby.store/api/v1/mcp-server.php' --transport streamable-http
mcp_servers:
store-buynearby-mcp:
url: "https://buynearby.store/api/v1/mcp-server.php" {
"McpServers": {
"store-buynearby-mcp": {
"Transport": "http",
"Url": "https://buynearby.store/api/v1/mcp-server.php"
}
}
} assistant mcp add store-buynearby-mcp -t streamable-http -u 'https://buynearby.store/api/v1/mcp-server.php'
{
"mcpServers": {
"store-buynearby-mcp": {
"type": "http",
"url": "https://buynearby.store/api/v1/mcp-server.php"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
- New tool “get_todays_deals” functional
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 0
- Tool “book_courier” rewrote its description, which is the text the model reads security
- Schema quality: 161 → 189 ▼ functional
- Tool coverage: 36% → 45% ▲ functional
- “book_courier” added an optional parameter “booking_ref” cosmetic
- “book_courier” added an optional parameter “cancel_reason” cosmetic
- “book_courier” added an optional parameter “idempotency_key” cosmetic
- “book_courier” reworded the description of “customer_phone” cosmetic
- “book_courier” reworded the description of “delivery_address” cosmetic
- “book_courier” reworded the description of “pickup_address” cosmetic
- “book_courier” made “delivery_address” optional cosmetic
- “book_courier” made “pickup_address” optional cosmetic
- 10 Sept 26 +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.
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 24 Sept 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=*.buynearby.store | CN=YR1,O=Let's Encrypt,C=US | 8 Sept 2026 | 7 Dec 2026 | RSA 2048 | SHA256-RSA | 6d4ce34eff1fc41877d352212db616fa03a |
| SANs: *.buynearby.store, buynearby.store | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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. | present | 2327 | 13 | Verified |
| buynearby.store. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://buynearby.store/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://buynearby.store/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://buynearby.store/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://buynearby.store/api/v1/mcp-server.php |
| Authorisation server | https://buynearby.store |
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 | Inconclusive | 405 |
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 ~467
Get a courier price quote, book a REAL point-to-point courier/parcel delivery in Calgary, check a booking's status, or cancel one - no BuyNearby account needed. action:'book' immediately creates the booking and auto-assigns a driver if one is available, exactly like a human finishing the form at buynearby.store/courier-book.php; the response's booking_ref is a real, live booking, not a draft. Payment is a link texted to the customer afterward (this call never charges a card). Use action:'quote' first if you just need a price before the user has decided to book. Use action:'status' to check on an existing booking, and action:'cancel' to self-cancel one (only while it's still 'pending' or 'assigned' — once a driver has picked up the package, direct the customer to support instead).
| 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 ~77
Check live stock level for a specific product. Optionally filter by store. If the caller's API key is a store-scoped partner key, the result is limited to that key's own store regardless of store_id.
| 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 ~28
Get a list of local stores in Calgary with location info.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
No output schema declared.
No examples provided.
get_todays_deals ~109
Get today's real discounted products and active flash deals — products currently priced below their regular price, and time-limited flash deals. This is the actual sale/discount data; search_products has no discount flag so a text search for "sale" or "deals" won't find this.
| 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 ~265
Shop BuyNearby's real marketplace catalog: add multiple products (from one store or several) to a cart and check out as ONE real order in a single call - price/stock for every item is looked up from the live catalog server-side (you cannot supply your own price). Use this instead of place_order whenever the user wants more than one item, or items from different stores. Uses the exact same tax/delivery-fee/coupon pricing engine as the human checkout page, so the total you quote back to the user is authoritative. Creates a REAL order immediately - not a draft - visible right away in the store's dashboard for confirmation. Payment is a pre-authorization link texted/emailed to the customer (card held, not charged) - the actual charge happens once the store confirms.
| 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 ~184
Place an order for a single product from BuyNearby's own catalog (stores running the BuyNearby POS - stock/price are live and guaranteed). Requires API key authentication. A store-scoped partner key can only order products from its own store. Payment is a pre-authorization link texted/emailed to the customer (card is held, not charged) - the actual charge happens once the store confirms the order, not at booking time.
| 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 ~100
Search for products available at local Calgary stores. Returns product name, store, price, stock level, and store categories. Use this when the user asks about finding, buying, or locating any product locally.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City to search. Default: Calgary |
| 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 ~204
Book a REAL personal-shopper run - a BuyNearby driver goes into a named physical store, shops from the given item list, and delivers it. Works even for stores that aren't BuyNearby partners (set needs_verification expectations: our team calls ahead to confirm stock first for those). This immediately creates the order, exactly like a customer finishing the Shop & Deliver chat flow on buynearby.store - it is not a draft. Estimate each item's price yourself (or via search_products if it's a known BuyNearby-catalog item) since the customer is only charged the driver's actual receipt total afterward, not this estimate.
| 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.
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 78 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,434 tokens of context every time the server is loaded.
Does the BuyNearby MCP server require authentication?
Yes. BuyNearby asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the BuyNearby MCP server still maintained?
BuyNearby 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.