NoshUp: Meal Planning & Grocery Budget

io.github.navshaincPublished by GitHub account navshaincv1.0.1Updated Oct 24, 2026

Grocery meal planning, budgets, and flyer deals for Canadian households. Auth required.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Lets an assistant help with grocery meal planning, food budgets, and flyer deals for Canadian households.

What you can do
NoshUp is a remote MCP server for grocery meal planning aimed at Canadian households. Based on the registry description, it covers meal planning, grocery budgets, and flyer deals. No tool list is published, so the exact operations an assistant can call are not documented here.
When to use it
Consider it if you want an assistant to help plan meals and manage a grocery budget, especially around Canadian grocery flyer deals. It is less relevant if you do not shop for groceries in Canada or do not need meal-planning help.
Requirements
A remote endpoint at over streamable HTTP. The registry description states that authentication is required, but no credential names, environment variables, or headers are declared in the manifest.
Before you install
The description says authentication is required, yet the manifest declares no authentication method, environment variables, or headers, so it is unclear what credentials you would be asked for. No tool list is published, so what the server can read or change is unknown. Review the provider's own terms and privacy information before connecting an account.

Installation

In SourceWeft

  1. Open NoshUp: Meal Planning & Grocery Budget in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.navshainc%2Fnoshup/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "noshup-meal-planning-grocery-budget": {
      "type": "http",
      "url": "https://api.noshup.ca/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.