NoshUp: Canadian Grocery Deals & Recipes
REMOTE · API.NOSHUP.CA
Canadian grocery flyer deals and recipes by item, store, postal code, cuisine, or diet. No auth.
Available components
Last scanned (13 hours ago)
Scores higher than 12% of remote servers
Reachable. Last reached 23 Oct 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 Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 28 Sept 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
- 25 Sept 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
- 22 Sept 26 +3
- Endpoint reachability: not serving MCP → behind authorisation ▼ security
- Authorization: unverified → fail ▼ security
- Transport: fail → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- HSTS header: pass → fail ▼ security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
- 20 Sept 26 −63
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Stability: 0.90 → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 16 Sept 26 0
- Transport: fail → pass ▲ security
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Sept 26 0
- Transport: pass → fail ▼ security
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 3 Sept 26 0
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.37 ▲ functional
- 2 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.30 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → 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 23 Oct 2026 · Probed https://api.noshup.ca/mcp-public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=noshup.ca | CN=WE1,O=Google Trust Services,C=US | 7 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 151642dacf2f6d100ec848cce2aa2095 |
| SANs: noshup.ca, *.noshup.ca | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.noshup.ca. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ca. | present | 26384 | 13 | Verified |
| noshup.ca. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 403 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.noshup.ca/mcp-public | Auth required | 403 | |
| http (plaintext) | http://api.noshup.ca/mcp-public | Inconclusive | 403 |
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 →
get_flyer_deals Find grocery deals ~131
Search current Canadian grocery flyer deals by item name or store. Covers FreshCo, Costco, Walmart, Food Basics, and more. All returned deals are currently valid and from the latest successful flyer fetch per store.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results |
| postal_code | – | – | Canadian postal code for location-aware deals (e.g. L4B1C3) |
| query | – | – | Item name to search deals for (e.g. paneer, milk, rice) |
| store | – | – | Filter by store name (e.g. FreshCo, Costco) |
Structured output declared, but exposes no named fields.
No examples provided.
get_recipe Get recipe ~42
Get full recipe details for a specific meal, including scaled ingredients and steps.
| Name | Type | Req | Description |
|---|---|---|---|
| meal_id | string | yes | Meal ID from search_meals (UUID) |
Structured output declared, but exposes no named fields.
No examples provided.
search_meals Search meals ~106
Search NoshUp's recipe catalogue by cuisine, dietary preference, ingredient, or meal type. The query matches both meal names and recipe ingredients.
| Name | Type | Req | Description |
|---|---|---|---|
| cuisine | – | – | Filter by cuisine |
| dietary | – | – | Dietary constraints (vegetarian, vegan, gluten_free, nut_allergy) |
| limit | integer | – | Maximum number of results |
| meal_type | – | – | Filter by meal type |
| query | – | – | Dish name, cuisine type, or ingredient to search for |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the NoshUp: Canadian Grocery Deals & Recipes MCP server?
NoshUp: Canadian Grocery Deals & Recipes is a hosted endpoint at https://api.noshup.ca/mcp-public, 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 · api.noshup.ca
claude mcp add --transport http navshainc-noshup-public 'https://api.noshup.ca/mcp-public'
What is the NoshUp: Canadian Grocery Deals & Recipes MCP server?
NoshUp: Canadian Grocery Deals & Recipes is an MCP server listed in the public MCP registry as io.github.navshainc/noshup-public. Canadian grocery flyer deals and recipes by item, store, postal code, cuisine, or diet. No auth. This page covers its hosted endpoint (https://api.noshup.ca/mcp-public).
Is the NoshUp: Canadian Grocery Deals & Recipes MCP server safe to use?
NoshUp: Canadian Grocery Deals & Recipes scores 28 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 NoshUp: Canadian Grocery Deals & Recipes MCP server expose?
NoshUp: Canadian Grocery Deals & Recipes exposes 3 tools: search_meals, get_recipe, get_flyer_deals. Their descriptions and schemas cost roughly 279 tokens of context every time the server is loaded.
Does the NoshUp: Canadian Grocery Deals & Recipes MCP server require authentication?
Yes. NoshUp: Canadian Grocery Deals & Recipes 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 NoshUp: Canadian Grocery Deals & Recipes MCP server still maintained?
NoshUp: Canadian Grocery Deals & Recipes is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.