run_shopping_discoveryLABSCO SUMMARY
Discovery across independent merchants, stopping deliberately short of checkout.
The boundary is the design: it returns products and merchant links and never takes a payment, so an agent can shop without your product inheriting a payments problem.
What it is
A hosted, closed-source MCP server for product discovery across independent stores on the open merchant web. One call takes a natural-language shopping intent and returns ranked results — best picks, alternatives, bundles, caveats, prices and merchant links. It stops at discovery: no checkout, no payment, no orders.
What you get
- A natural-language shopping intent turned into ranked product results
- Best picks, alternatives, bundles and caveats, with prices and links back to the merchant
- A completed discovery fetched again by result_id
- Feedback reported against a result you were given
- The stores it covers, listed
- A purchase_boundary block on every response, restating that the purchase happens on the merchant's own site
Requirements
Nothing to install — connect to https://mcp.periskop.ai/v1/mcp over Streamable HTTP with a Periskop API key as a bearer token. OAuth with PKCE is supported for hosts that prefer it; unauthenticated requests are refused with a WWW-Authenticate: Bearer header.
Setup effort
Add the configuration to your client
USE CASES
01
Turning a request into things you can actually buy
One call takes the sentence and returns ranked products with prices and merchant links.
02
Picking a result up again later
Fetch a completed discovery by its result id.
03
Sourcing across suppliers rather than one store
Results come from independent stores on the open merchant web, and the covered stores can be listed.
04
Making the ranking better over time
Report feedback against a result you were given.
5 tools
Listed in project docs. Your client may show a different list.
get_discovery_resultdiscover_supported_storesreport_result_feedbacksuggest_store_coverageBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
INSTALLATION
Connect your client
MCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add --transport http periskop https://mcp.periskop.ai/v1/mcp \
--header "Authorization: Bearer <YOUR_PERISKOP_API_KEY>"Claude Desktop
Periskop is a remote Streamable-HTTP server; Desktop reaches it through the mcp-remote stdio bridge. <YOUR_PERISKOP_API_KEY> is your Periskop API key. Get a key at https://periskop.ai/developer
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"periskop": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.periskop.ai/v1/mcp",
"--header",
"Authorization: Bearer <YOUR_PERISKOP_API_KEY>"
]
}
}
}Cursor
CURSOR · JSON
{
"mcpServers": {
"periskop": {
"url": "https://mcp.periskop.ai/v1/mcp",
"headers": {
"Authorization": "Bearer <YOUR_PERISKOP_API_KEY>"
}
}
}
}
