GroceryPulse Canada
REMOTE · GROCERYPULSE.CA
Read-only grocery-list comparisons for supported Canadian cities, with dated prices and coverage.
Available components
Last scanned (1 hour ago)
Scores higher than 84% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 939 tokens (~313/item across 3 items; 3 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 Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 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.
- 27 Oct 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.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +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.
- 21 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “compare_grocery_list” rewrote its description, which is the text the model reads security
- Tool “get_grocery_catalog” rewrote its description, which is the text the model reads security
- Tool “plan_grocery_order” rewrote its description, which is the text the model reads security
- Schema quality: 248 → 313 ▼ functional
- Server version: 1.0.0 → 1.1.0 functional
- “compare_grocery_list” reworded the description of “items” cosmetic
- “plan_grocery_order” reworded the description of “city” cosmetic
- “plan_grocery_order” reworded the description of “postalCode” cosmetic
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 5 Nov 2026 · Probed https://grocerypulse.ca/api/shopper/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=grocerypulse.ca | CN=YR2,O=Let's Encrypt,C=US | 17 Oct 2026 | 15 Jan 2027 | RSA 4096 | SHA256-RSA | 527c89e6df41416724c3d43d62eec4f2058 |
| SANs: grocerypulse.ca, www.grocerypulse.ca | ||||||
| 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 grocerypulse.ca. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ca. | present | 26384 | 13 | Verified |
| grocerypulse.ca. | absent | 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=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://grocerypulse.ca/api/shopper/mcp | Verified | 200 | |
| http (plaintext) | http://grocerypulse.ca/api/shopper/mcp | HTTPS enforced | 301 | https://grocerypulse.ca/api/shopper/mcp |
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 →
compare_grocery_list Compare a Canadian grocery list ~250
Compares current public chain prices for a list of catalogue item ids (from get_grocery_catalog) and quantities in one supported Canadian city; plan_grocery_order is the form that takes a list in the shopper's own words. A lowest-chain recommendation requires fresh full requested coverage at two eligible chains with no close call or package/reference-size reversal. Results keep missing items, exclusions, price dates, scope and source links, and each chain includes plain per-item storeLinks to its own product page or search, with the price date used. Each id is one product at its catalogue size (for example 4 L milk); a different size, variant or brand is a different product. Chain medians are not branch stock or guaranteed checkout quotes. Read-only: it does not buy, save a list, send email or access licensed or private data.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | – |
| items | array | yes | IDs must be unique. Each id is one product at one package size (its catalogue name and referenceSize); a different size, variant or brand is a different product (for example, the catalogue's 4 L milk… |
| stores | array | – | – |
No output schema declared.
No examples provided.
get_grocery_catalog Canadian grocery comparison catalogue ~86
Lists GroceryPulse's configured Canadian cities, canonical reference items with their ids, quantity units, known chains and checkout eligibility holds: the ids that compare_grocery_list takes. Configured coverage is not current availability or coverage of every nearby branch. Each item is one product at one package size (its name and referenceSize); a different size, variant or brand is a different product.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
plan_grocery_order Plan a Canadian grocery order ~447
Plans a grocery order from a shopping list as the shopper wrote it, in a covered Canadian city. Use when a shopper asks where their list is cheapest or wants to buy groceries online. Takes the list as text (English or French, quantities included, up to 60 lines), the city or the first three characters of a postal code inside it and, optionally, the stores the shopper uses. Returns each line as exact, closest (a different size, variant or brand: not priced and in no total) or not tracked; per-store totals with coverage and price dates; a cheapest store only when every compared item is priced at two or more chains with a clear lead (or, when the only obstacle is a pack item whose count no store's listing gives, a store labelled cheapest for the other lines, with those lines listed apart), otherwise the reason; per-item links to each store's own product page or search; and interpretation notes that state what the result does and does not cover. Read-only: it never orders, adds to a cart, saves a list or contacts a store.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | The covered Canadian city whose chain prices are compared (the price market): its English or French name, or its slug. Give this or postalCode. |
| language | string | – | Language for item names and store links. Default en. |
| list | string | yes | The shopper's grocery list exactly as they wrote it, one item per line (or comma-separated), English or French, with quantities if they gave them: "2L milk", "dozen eggs", "3 lbs lean ground beef", "… |
| postalCode | string | – | The first three characters of a Canadian postal code (the forward sortation area, for example K1P), used only to choose the covered city. Areas outside the covered cities are refused, never moved to… |
| stores | array | – | Optional: only the stores the shopper is willing to use (names like "No Frills" or catalogue keys). Omit to compare every tracked chain in the city. |
No output schema declared.
No examples provided.
How do I install the GroceryPulse Canada MCP server?
GroceryPulse Canada is a hosted endpoint at https://grocerypulse.ca/api/shopper/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.
remote · grocerypulse.ca
claude mcp add --transport http ca-grocerypulse-grocery-comparison 'https://grocerypulse.ca/api/shopper/mcp'
What is the GroceryPulse Canada MCP server?
GroceryPulse Canada is an MCP server listed in the public MCP registry as ca.grocerypulse/grocery-comparison. Read-only grocery-list comparisons for supported Canadian cities, with dated prices and coverage. This page covers its hosted endpoint (https://grocerypulse.ca/api/shopper/mcp).
Is the GroceryPulse Canada MCP server safe to use?
GroceryPulse Canada scores 81 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 GroceryPulse Canada MCP server expose?
GroceryPulse Canada exposes 3 tools: plan_grocery_order, get_grocery_catalog, compare_grocery_list. Their descriptions and schemas cost roughly 783 tokens of context every time the server is loaded.
Does the GroceryPulse Canada MCP server require authentication?
No. We connected to GroceryPulse Canada without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the GroceryPulse Canada MCP server still maintained?
GroceryPulse Canada is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.