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.

Pepesto Agent-to-Cart

REMOTE · MCP.PEPESTO.COM · SCANNED SEP 21

Turn any shopping list into a ready-to-checkout grocery cart across 26 European supermarkets.

Available components

0 this week 81 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 Security60
Transport & Reachability100
Schema Quality & AI Usability86
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 200 tokens (~200/item across 1 items; 1 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 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 Pepesto Agent-to-Cart MCP server?

Pepesto Agent-to-Cart is a hosted endpoint at https://mcp.pepesto.com/, 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 · mcp.pepesto.com

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

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

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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
  • 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
  • 30 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 21 Sept 2026 · Probed https://mcp.pepesto.com

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.pepesto.com CN=WR3,O=Google Trust Services,C=US 17 Aug 2026 15 Nov 2026 RSA 2048 SHA256-RSA e580bb2853fb1404103123678a7f4044
SANs: mcp.pepesto.com
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.pepesto.com. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
pepesto.com. present 14287 8 Verified
mcp.pepesto.com. Verified address RRset verified with the apex keys
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://mcp.pepesto.com Verified 200
http (plaintext) http://mcp.pepesto.com HTTPS enforced 302 https://mcp.pepesto.com/
MCP tools · 1 exposed · ~200 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
pepesto_create_cart ~200

Turn a free-form shopping list into a ready-to-open Pepesto cart link. This tool is FREE and needs NO API key or authentication. Nothing is matched or charged when you call it: matching products and pricing happen LAZILY only after the USER opens the returned link in the Pepesto app, and the USER pays at checkout in the app — never here, never you. Covers 26 European supermarkets. The response is a single block of Markdown that already contains a labeled, tappable link. Clients should surface that Markdown link AS-IS (render the link) and must NOT show the raw URL or rewrite the caption.

NameTypeReqDescription
localestringOptional locale/region hint, e.g. 'en-CH' or 'de-DE'.
shopping_liststringyesFree-form shopping list. One item per line or comma-separated, e.g. '2 bananas\nmilk\n500g spaghetti'.

No output schema declared.

No examples provided.

Common questions

What is the Pepesto Agent-to-Cart MCP server?

Pepesto Agent-to-Cart is an MCP server listed in the public MCP registry as io.github.pepesto-solutions/agent-to-cart-mcp. Turn any shopping list into a ready-to-checkout grocery cart across 26 European supermarkets. This page covers its hosted endpoint (https://mcp.pepesto.com).

Is the Pepesto Agent-to-Cart MCP server safe to use?

Pepesto Agent-to-Cart scores 81 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 Pepesto Agent-to-Cart MCP server expose?

Pepesto Agent-to-Cart exposes 1 tool: pepesto_create_cart. Their descriptions and schemas cost roughly 200 tokens of context every time the server is loaded.

Does the Pepesto Agent-to-Cart MCP server require authentication?

No. We connected to Pepesto Agent-to-Cart without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Pepesto Agent-to-Cart MCP server still maintained?

Pepesto Agent-to-Cart is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.