_ registry / mcp http-sse · checked 3h ago

Forage Shopping

https://forageshopping.com

Registry code: 7ebce8b81de541e4

api record

Search and compare products across merchants. Find the best deals. When the user wants to buy, use start_checkout with the product URL to begin a UCP checkout session. Pass the same session_id across search and checkout tools to track which content influenced the purchase.

endpoint
https://forageshopping.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Forage Shopping live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is Forage Shopping free to use?
Yes — the hub reached it with no key and no payment.
What tools does Forage Shopping have?
7 tools: compare_prices, start_checkout, update_checkout_info, complete_purchase, check_order, find_deals, search_products.
Is Forage Shopping safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.6%· all time 99.6%

latency
246ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 274 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • search products across merchants
  • compare prices for a product
  • find deals in a category
  • start a checkout for a product
  • complete a purchase
takes → gives
text → data, payments
tools
4 reads2 changes data1 moves money
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 7 tools
7 never probed 0 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • compare_prices reads unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "title": "compare_pricesArguments",
      "required": [
        "product_name"
      ],
      "properties": {
        "session_id": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Session Id",
          "default": null,
          "description": "Optional session identifier to link tool calls in one conversation."
        },
        "product_name": {
          "type": "string",
          "title": "Product Name",
          "description": "Specific product to compare prices for, e.g. 'Nike Pegasus 41'"
        }
      }
    }
    arguments 27 lines
  • start_checkout changes data unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "title": "start_checkoutArguments",
      "required": [
        "product_url"
      ],
      "properties": {
        "quantity": {
          "type": "integer",
          "title": "Quantity",
          "default": 1,
          "description": "Number of items to purchase"
        },
        "session_id": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Session Id",
          "default": null,
          "description": "Session identifier to link checkout with earlier search telemetry."
        },
        "product_url": {
          "type": "string",
          "title": "Product Url",
          "description": "URL of the product to purchase. The merchant's domain is used for UCP discovery."
        }
      }
    }
    arguments 33 lines
  • update_checkout_info changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "title": "update_checkout_infoArguments",
      "required": [
        "checkout_id"
      ],
      "properties": {
        "buyer_name": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Buyer Name",
          "default": null,
          "description": "Buyer's full name"
        },
        "buyer_email": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Buyer Email",
          "default": null,
          "description": "Buyer's email address"
        },
        "checkout_id": {
          "type": "string",
          "title": "Checkout Id",
          "description": "The checkout session ID from start_checkout"
        },
        "discount_code": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Discount Code",
          "default": null,
          "description": "Discount or promo code to apply"
        },
        "shipping_address": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Shipping Address",
          "default": null,
          "description": "Shipping address as a single string (the merchant will parse it)"
        }
      }
    }
    arguments 66 lines
  • complete_purchase moves money unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "title": "complete_purchaseArguments",
      "required": [
        "checkout_id"
      ],
      "properties": {
        "session_id": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Session Id",
          "default": null,
          "description": "Session identifier for telemetry. Use the same one from search/checkout."
        },
        "checkout_id": {
          "type": "string",
          "title": "Checkout Id",
          "description": "The checkout session ID to complete"
        }
      }
    }
    arguments 27 lines
  • check_order reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "title": "check_orderArguments",
      "required": [
        "checkout_id"
      ],
      "properties": {
        "checkout_id": {
          "type": "string",
          "title": "Checkout Id",
          "description": "The checkout session ID to check"
        }
      }
    }
    arguments 14 lines
  • find_deals reads unknown 22h ago

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

    mcp-tool

    {
      "type": "object",
      "title": "find_dealsArguments",
      "required": [
        "category"
      ],
      "properties": {
        "budget": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Budget",
          "default": null,
          "description": "Optional budget limit, e.g. '£100', '$50'"
        },
        "category": {
          "type": "string",
          "title": "Category",
          "description": "Product category, e.g. 'headphones', 'running shoes', 'coffee machines'"
        },
        "session_id": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Session Id",
          "default": null,
          "description": "Optional session identifier to link tool calls in one conversation."
        }
      }
    }
    arguments 40 lines
  • search_products reads unknown 22h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "search_productsArguments",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "title": "Query",
          "description": "What to search for, e.g. 'running shoes under £120'"
        },
        "session_id": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Session Id",
          "default": null,
          "description": "Optional session identifier to link tool calls in one conversation. Pass a stable string (e.g. conversation ID) across multiple tool calls."
        },
        "max_results": {
          "type": "integer",
          "title": "Max Results",
          "default": 10,
          "description": "Maximum number of results to return"
        }
      }
    }
    arguments 33 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 7ebce8b81de541e4.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/7ebce8b81de541e4/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/7ebce8b81de541e4/badge.svg)](https://brick.blue/agent/7ebce8b81de541e4?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.