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.

Jewelry by Sweet Pea Products

REMOTE · CHAT.JEWELRYBYSWEETPEA.COM · SCANNED SEP 20

Live fine-jewelry catalog: search, product lookup, compatible chains, size/length variants, store po

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 Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 381 tokens (~76/item across 5 items; 5 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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 Jewelry by Sweet Pea Products MCP server?

Jewelry by Sweet Pea Products is a hosted endpoint at https://chat.jewelrybysweetpea.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 · chat.jewelrybysweetpea.com

# add to Claude Code
claude mcp add --transport http danielle790-jewelry-by-sweet-pea 'https://chat.jewelrybysweetpea.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "danielle790-jewelry-by-sweet-pea": {
      "url": "https://chat.jewelrybysweetpea.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "danielle790-jewelry-by-sweet-pea": {
      "type": "http",
      "url": "https://chat.jewelrybysweetpea.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.danielle790-jewelry-by-sweet-pea]
url = "https://chat.jewelrybysweetpea.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "danielle790-jewelry-by-sweet-pea": {
      "type": "remote",
      "url": "https://chat.jewelrybysweetpea.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add danielle790-jewelry-by-sweet-pea --url 'https://chat.jewelrybysweetpea.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  danielle790-jewelry-by-sweet-pea:
    url: "https://chat.jewelrybysweetpea.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "danielle790-jewelry-by-sweet-pea": {
      "Transport": "http",
      "Url": "https://chat.jewelrybysweetpea.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add danielle790-jewelry-by-sweet-pea -t streamable-http -u 'https://chat.jewelrybysweetpea.com/mcp'
// mcp.json
{
  "mcpServers": {
    "danielle790-jewelry-by-sweet-pea": {
      "type": "http",
      "url": "https://chat.jewelrybysweetpea.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.

  • 5 Sept 26 +1
    • Schema quality: 65 → 76 functional
    • Schema quality: good → excellent functional
    • New tool “find_compatible_chains” functional
    • New tool “list_size_variants” functional
  • 29 Aug 26 0
    • Stability: 0.97 → pass security
  • 27 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.

  • 26 Aug 26 +1
    • 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

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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

    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://chat.jewelrybysweetpea.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=chat.jewelrybysweetpea.com CN=YE1,O=Let's Encrypt,C=US 8 Sept 2026 7 Dec 2026 ECDSA 256 ECDSA-SHA384 51e615efd121cb75e353152b514fdc3c44c
SANs: chat.jewelrybysweetpea.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 chat.jewelrybysweetpea.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
jewelrybysweetpea.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://chat.jewelrybysweetpea.com/mcp Verified 200
http (plaintext) http://chat.jewelrybysweetpea.com/mcp HTTPS enforced 308 https://chat.jewelrybysweetpea.com/mcp
MCP tools · 5 exposed · ~381 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
find_compatible_chains ~93

For a pendant or charm SKU, returns chains whose width fits the pendant's bail (same metal family, sensible width and price), plus other pieces the store pairs with it (same school/team or same collection). Use get_product on a returned name/URL for live price and stock.

NameTypeReqDescription
skustringyesThe pendant/charm SKU, e.g. K4324 or 4Y001CU.

No output schema declared.

No examples provided.

get_product ~48

Fetch one product's live details (price, availability, sizes/variants, URL) by its SKU.

NameTypeReqDescription
skustringyesThe product SKU, e.g. GP016MIS-18.

No output schema declared.

No examples provided.

get_store_policies ~38

Shipping (free US), returns (free 30-day), warranty, resizing, payment, and contact details for Jewelry by Sweet Pea.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_size_variants ~92

For a ring, chain, bracelet or anklet SKU, lists the sibling products that are the same piece in other sizes (ring sizes) or lengths (inches), each with its own SKU and URL. Empty when the piece comes in one size.

NameTypeReqDescription
skustringyesA SKU such as WCF040-5 (ring size 5) or BOX100-14 (14 inch chain).

No output schema declared.

No examples provided.

search_products ~110

Live search of 100,000+ fine-jewelry products (gold, sterling silver, NCAA/collegiate LogoArt). Returns name, SKU, live price, availability, product URL, and image. Best queries are short and specific (e.g. 'alabama pendant', '14k rope chain 20 inch').

NameTypeReqDescription
max_resultsintegerMax products to return (default 6).
querystringyesSearch terms (product type, school/team, metal, style).

No output schema declared.

No examples provided.

Common questions

What is the Jewelry by Sweet Pea Products MCP server?

Jewelry by Sweet Pea Products is an MCP server listed in the public MCP registry as io.github.danielle790/jewelry-by-sweet-pea. Live fine-jewelry catalog: search, product lookup, compatible chains, size/length variants, store po. This page covers its hosted endpoint (https://chat.jewelrybysweetpea.com/mcp).

Is the Jewelry by Sweet Pea Products MCP server safe to use?

Jewelry by Sweet Pea Products 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 Jewelry by Sweet Pea Products MCP server expose?

Jewelry by Sweet Pea Products exposes 5 tools: search_products, get_product, find_compatible_chains, list_size_variants, get_store_policies. Their descriptions and schemas cost roughly 381 tokens of context every time the server is loaded.

Does the Jewelry by Sweet Pea Products MCP server require authentication?

No. We connected to Jewelry by Sweet Pea Products without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Jewelry by Sweet Pea Products MCP server still maintained?

Jewelry by Sweet Pea Products 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.