Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Forage Shopping

REMOTE · FORAGESHOPPING.COM · SCANNED SEP 20

AI shopping comparison — search 50M+ products, compare prices, find deals

0 this week 79 Trust /100
Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 766 tokens (~109/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Forage Shopping MCP server?

Forage Shopping is a hosted endpoint at https://forageshopping.com/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 · forageshopping.com

# add to Claude Code
claude mcp add --transport http jalexspringer-forage-shopping 'https://forageshopping.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "jalexspringer-forage-shopping": {
      "url": "https://forageshopping.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "jalexspringer-forage-shopping": {
      "type": "http",
      "url": "https://forageshopping.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.jalexspringer-forage-shopping]
url = "https://forageshopping.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jalexspringer-forage-shopping": {
      "type": "remote",
      "url": "https://forageshopping.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add jalexspringer-forage-shopping --url 'https://forageshopping.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  jalexspringer-forage-shopping:
    url: "https://forageshopping.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "jalexspringer-forage-shopping": {
      "Transport": "http",
      "Url": "https://forageshopping.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add jalexspringer-forage-shopping -t streamable-http -u 'https://forageshopping.com/mcp'
// mcp.json
{
  "mcpServers": {
    "jalexspringer-forage-shopping": {
      "type": "http",
      "url": "https://forageshopping.com/mcp"
    }
  }
}

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

Changelog

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.

  • 26 Aug 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 Aug 26 +1
    • Stability: 0.97 → pass security
  • 23 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 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
  • 7 Aug 26 0
    • The server no longer declares the “experimental” capability functional
  • 31 Jul 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
  • 27 Jul 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
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

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 20 Sept 2026 · Probed https://forageshopping.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=forageshopping.com CN=YE1,O=Let's Encrypt,C=US 20 Aug 2026 18 Nov 2026 ECDSA 256 ECDSA-SHA384 62c964f6448d211d466c6d6992412e99e47
SANs: forageshopping.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of forageshopping.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
forageshopping.com. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://forageshopping.com/mcp Verified 200
http (plaintext) http://forageshopping.com/mcp HTTPS enforced 301 https://forageshopping.com/mcp
MCP tools · 7 exposed · ~711 tokens

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 →

Tool Tokens
check_order ~72

Check the status of a checkout session or order. Use this after the user has completed an escalation step (e.g. payment in the browser) to see if the checkout can now proceed, or to check on a completed order's status.

NameTypeReqDescription
checkout_idstringyesThe checkout session ID to check
NameTypeReqDescription
resultstringyes

No examples provided.

compare_prices ~70

Compare prices for a specific product across multiple merchants. Finds the same product at different retailers and shows price differences.

NameTypeReqDescription
product_namestringyesSpecific product to compare prices for, e.g. 'Nike Pegasus 41'
session_idOptional session identifier to link tool calls in one conversation.
NameTypeReqDescription
resultstringyes

No examples provided.

complete_purchase ~89

Complete a checkout and place the order. Only call this when the checkout status is 'ready_for_complete'. Records the purchase as a conversion in telemetry and ends the attribution session. Returns the order confirmation with order ID and receipt link.

NameTypeReqDescription
checkout_idstringyesThe checkout session ID to complete
session_idSession identifier for telemetry. Use the same one from search/checkout.
NameTypeReqDescription
resultstringyes

No examples provided.

find_deals ~90

Find the best current deals in a product category. Searches for discounted, on-sale, or best-value products.

NameTypeReqDescription
budgetOptional budget limit, e.g. '£100', '$50'
categorystringyesProduct category, e.g. 'headphones', 'running shoes', 'coffee machines'
session_idOptional session identifier to link tool calls in one conversation.
NameTypeReqDescription
resultstringyes

No examples provided.

search_products ~127

Search for products across merchants and return comparison results. Returns structured product listings with prices, merchants, and checkout links. Searches Shopify's global catalogue (50M+ products across all Shopify merchants) and Channel3's affiliate network. Results include direct checkout links.

NameTypeReqDescription
max_resultsintegerMaximum number of results to return
querystringyesWhat to search for, e.g. 'running shoes under £120'
session_idOptional session identifier to link tool calls in one conversation. Pass a stable string (e.g. conversation ID) across multiple tool calls.
NameTypeReqDescription
resultstringyes

No examples provided.

start_checkout ~119

Start a UCP checkout session for a product. Discovers the merchant's UCP capabilities, creates a checkout session, and attaches content attribution data from the current session's search and comparison activity. Returns the checkout status and any information the merchant still needs (email, shipping address, etc).

NameTypeReqDescription
product_urlstringyesURL of the product to purchase. The merchant's domain is used for UCP discovery.
quantityintegerNumber of items to purchase
session_idSession identifier to link checkout with earlier search telemetry.
NameTypeReqDescription
resultstringyes

No examples provided.

update_checkout_info ~144

Update a checkout session with buyer information. Provide the information the merchant requested (email, name, shipping address, discount codes). Call this after start_checkout when the merchant indicates what information is still needed. If the response has status 'requires_escalation', share the continue_url with the user so they can complete payment in their browser.

NameTypeReqDescription
buyer_emailBuyer's email address
buyer_nameBuyer's full name
checkout_idstringyesThe checkout session ID from start_checkout
discount_codeDiscount or promo code to apply
shipping_addressShipping address as a single string (the merchant will parse it)
NameTypeReqDescription
resultstringyes

No examples provided.

Common questions

What is the Forage Shopping MCP server?

Forage Shopping is an MCP server listed in the public MCP registry as io.github.jalexspringer/forage-shopping. AI shopping comparison, search 50M+ products, compare prices, find deals. This page covers its hosted endpoint (https://forageshopping.com/mcp).

Is the Forage Shopping MCP server safe to use?

Forage Shopping scores 79 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 Forage Shopping MCP server expose?

Forage Shopping exposes 7 tools: search_products, compare_prices, find_deals, start_checkout, update_checkout_info, and 2 more. Their descriptions and schemas cost roughly 711 tokens of context every time the server is loaded.

Does the Forage Shopping MCP server require authentication?

No. We connected to Forage Shopping without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Forage Shopping MCP server still maintained?

Forage Shopping is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.