Forage Shopping

REMOTE · FORAGESHOPPING.COM · SCANNED AUG 3

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

Available components

+3 this week 67 67 Trust /100

Trust breakdown (6 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 →

Endpoint Security57

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
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 & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability77

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 Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · forageshopping.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http jalexspringer-forage-shopping 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"

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

2 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
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
29 Jul 26 +1

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

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
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 64

First indexed and scored.

Show 5 earlier entries Hide earlier entries

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 3 Aug 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	21 Jun 2026	19 Sept 2026	ECDSA 256	ECDSA-SHA384	5e64d323245ab404b088b1218af71e27b7f
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

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

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.

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.

Input Output Examples

Name	Type	Req	Description
checkout_id	string	yes	The checkout session ID to check

Name	Type	Req	Description
result	string	yes	—

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.

Input Output Examples

Name	Type	Req	Description
product_name	string	yes	Specific product to compare prices for, e.g. 'Nike Pegasus 41'
session_id	—	—	Optional session identifier to link tool calls in one conversation.

Name	Type	Req	Description
result	string	yes	—

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.

Input Output Examples

Name	Type	Req	Description
checkout_id	string	yes	The checkout session ID to complete
session_id	—	—	Session identifier for telemetry. Use the same one from search/checkout.

Name	Type	Req	Description
result	string	yes	—

No examples provided.

find_deals ~90

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

Input Output Examples

Name	Type	Req	Description
budget	—	—	Optional budget limit, e.g. '£100', '$50'
category	string	yes	Product category, e.g. 'headphones', 'running shoes', 'coffee machines'
session_id	—	—	Optional session identifier to link tool calls in one conversation.

Name	Type	Req	Description
result	string	yes	—

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.

Input Output Examples

Name	Type	Req	Description
max_results	integer	—	Maximum number of results to return
query	string	yes	What to search for, e.g. 'running shoes under £120'
session_id	—	—	Optional session identifier to link tool calls in one conversation. Pass a stable string (e.g. conversation ID) across multiple tool calls.

Name	Type	Req	Description
result	string	yes	—

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

Input Output Examples

Name	Type	Req	Description
product_url	string	yes	URL of the product to purchase. The merchant's domain is used for UCP discovery.
quantity	integer	—	Number of items to purchase
session_id	—	—	Session identifier to link checkout with earlier search telemetry.

Name	Type	Req	Description
result	string	yes	—

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.

Input Output Examples

Name	Type	Req	Description
buyer_email	—	—	Buyer's email address
buyer_name	—	—	Buyer's full name
checkout_id	string	yes	The checkout session ID from start_checkout
discount_code	—	—	Discount or promo code to apply
shipping_address	—	—	Shipping address as a single string (the merchant will parse it)

Name	Type	Req	Description
result	string	yes	—

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	64
27 Jul	64
28 Jul	65
29 Jul	66
30 Jul	66
31 Jul	66
1 Aug	66
2 Aug	67
3 Aug	67