# GroceryPulse Canada (remote · grocerypulse.ca)

Read-only grocery-list comparisons for supported Canadian cities, with dated prices and coverage.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `grocerypulse.ca`: 81/100 (this document), [markdown](https://verifymcp.io/servers/ca-grocerypulse-grocery-comparison/api-shopper-mcp.md), [page](https://verifymcp.io/servers/ca-grocerypulse-grocery-comparison/api-shopper-mcp)

## Channel facts

- Endpoint: `https://grocerypulse.ca/api/shopper/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http ca-grocerypulse-grocery-comparison 'https://grocerypulse.ca/api/shopper/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ca-grocerypulse-grocery-comparison": {
      "url": "https://grocerypulse.ca/api/shopper/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ca-grocerypulse-grocery-comparison": {
      "type": "http",
      "url": "https://grocerypulse.ca/api/shopper/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ca-grocerypulse-grocery-comparison]
url = "https://grocerypulse.ca/api/shopper/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ca-grocerypulse-grocery-comparison": {
      "type": "remote",
      "url": "https://grocerypulse.ca/api/shopper/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ca-grocerypulse-grocery-comparison --url 'https://grocerypulse.ca/api/shopper/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ca-grocerypulse-grocery-comparison:
    url: "https://grocerypulse.ca/api/shopper/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ca-grocerypulse-grocery-comparison": {
      "Transport": "http",
      "Url": "https://grocerypulse.ca/api/shopper/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ca-grocerypulse-grocery-comparison -t streamable-http -u 'https://grocerypulse.ca/api/shopper/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ca-grocerypulse-grocery-comparison": {
      "type": "http",
      "url": "https://grocerypulse.ca/api/shopper/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 81, +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.

### 2026-11-02 (score 80, +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.

### 2026-10-31 (score 79, +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.

### 2026-10-29 (score 78, +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.

### 2026-10-27 (score 77, +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.

### 2026-10-25 (score 76, +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.

### 2026-10-23 (score 75, +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.

### 2026-10-21 (score 74, −1)

- [security] 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
- [functional regression] Schema quality: 248 → 313
- [functional] Server version: 1.0.0 → 1.1.0
- [cosmetic] “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”

## MCP tools (3)

### `plan_grocery_order` (~447 tokens)

Plan a Canadian grocery order

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.

Input parameters:

- `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, required): 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.

### `get_grocery_catalog` (~86 tokens)

Canadian grocery comparison catalogue

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.

### `compare_grocery_list` (~250 tokens)

Compare a Canadian grocery list

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.

Input parameters:

- `city` (string, required)
- `items` (array, required): 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)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ca-grocerypulse-grocery-comparison/api-shopper-mcp#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 78
- 2026-10-29: 78
- 2026-10-28: 77
- 2026-10-27: 77
- 2026-10-26: 76
- 2026-10-25: 76
- 2026-10-24: 75
- 2026-10-23: 75
- 2026-10-22: 74
- 2026-10-21: 74
- 2026-10-20: 75
- 2026-10-19: 74
- 2026-10-18: 74
- 2026-10-17: 73
- 2026-10-16: 73
- 2026-10-15: 73
- 2026-10-14: 72
- 2026-10-13: 72
- 2026-10-12: 71

## Common questions

### 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.

## Links

- Remote endpoint: https://grocerypulse.ca/api/shopper/mcp
- Website: https://grocerypulse.ca/agents
- Changelog RSS feed: https://verifymcp.io/servers/ca-grocerypulse-grocery-comparison/api-shopper-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ca-grocerypulse-grocery-comparison/api-shopper-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ca-grocerypulse-grocery-comparison/api-shopper-mcp