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.

JoinTheDeal

REMOTE · JOINTHEDEAL.COM

Search Southern California home deals and group buys. Read-only, no login.

Available components

+3 this week 74 Trust /100

Last scanned (20 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1049 tokens (~209/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 81% of tool parameters carry a description.Partial
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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

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

  • 16 Nov 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.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_deal” rewrote its description, which is the text the model reads security
    • Tool “request_group_deal” rewrote its description, which is the text the model reads security
    • Tool “search_deals” rewrote its description, which is the text the model reads security
    • Schema quality: 886 → 1049 ▼ functional
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
    • Server version: 1.3.0 → 1.5.0 functional
    • New tool “search_requests” functional
    • “request_group_deal” added an optional parameter “model” cosmetic
    • “request_group_deal” reworded the description of “item” cosmetic
    • “search_deals” reworded the description of “deal_type” cosmetic
  • 11 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 10 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 9 Nov 26 68

    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 Nov 2026 · Probed https://jointhedeal.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.jointhedeal.com CN=YR1,O=Let's Encrypt,C=US 9 Oct 2026 7 Jan 2027 RSA 2048 SHA256-RSA 65fdd44fa10977d11ab60f48ab92021ead5
SANs: jointhedeal.com, www.jointhedeal.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of jointhedeal.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
jointhedeal.com. No DS 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://jointhedeal.com/mcp Verified 200
http (plaintext) http://jointhedeal.com/mcp HTTPS enforced 301 https://jointhedeal.com/mcp
MCP tools · 5 exposed · ~719 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
get_deal ~77

Full details of one deal by its id (from search_deals). Group deals include goal, joined (paid participants), deal window, what is included, region, payment terms (payment_short, deposit_text) and JoinTheDeal's own public-low price check when available.

NameTypeReqDescription
idintegeryesDeal id from search_deals.

No output schema declared.

No examples provided.

list_categories ~27

Categories and sellers that currently have deals, with counts, and when the data was last updated.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

request_group_deal ~137

Get the link to JoinTheDeal's request form for a product the user wants, and see first whether the same item is already requested or on sale as a group deal (then the user should join that instead). This tool does not submit anything and takes no personal information: the user opens the link and fills in the form themselves. When enough people back the same item with a refundable deposit, JoinTheDeal asks the seller for a group price.

NameTypeReqDescription
itemstring–Product name the user wants (optional). Do not include names, emails or phone numbers.
modelstring–Model number if known (optional).

No output schema declared.

No examples provided.

search_deals ~342

Search JoinTheDeal: group deals sold by JoinTheDeal (with goal, joined count, deal window, payment terms), requested deals (people gathering, no price yet) and Deal Finder offers from other sellers (comparison reference only). Results come in that order. Filter by keywords, category, event, seller and price range. If nothing of JoinTheDeal matches (jtd_match=false) the response carries request_url for the user to start a request.

NameTypeReqDescription
categorystring–Category or subcategory name or part of it (see list_categories), e.g. "Korean grocery", "Fishing", "Robot vacuums".
deal_typestring–group_deal = sold by JoinTheDeal; requested = people gathering for an item (no price yet); deal_finder = sold by another seller (comparison only).
eventstring–Event tag, e.g. "black-friday-2026" (deals the seller itself labels Black Friday / Cyber Monday). See list_categories events.
include_expiredboolean––
limitinteger––
max_pricenumber–Maximum price in USD.
min_pricenumber–Minimum price in USD. Offers without a single dollar price (e.g. "Up to $800 off") are left out when a price filter is used.
querystring–Keywords, e.g. "rice cooker", "air purifier", "mattress queen". All words must match.
sellerstring–Seller name or part of it, e.g. "CUCKOO", "LG", "H Mart".

No output schema declared.

No examples provided.

search_requests ~136

Requested deals: items shoppers asked JoinTheDeal to make a group deal for. Shows how many are waiting, how many paid a refundable deposit, the deposit goal and deadline, and the stage (requested / checking = asking the seller / open / closed). No price until a deal opens. No personal data.

NameTypeReqDescription
categorystring–Category slug or name part, e.g. kitchen, grocery, beauty, electronics, baby, pets.
limitinteger––
querystring–Keywords; all words must match the item name.
stagestring–active = requested + checking + open (default).

No output schema declared.

No examples provided.

Install

How do I install the JoinTheDeal MCP server?

JoinTheDeal is a hosted endpoint at https://jointhedeal.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 · jointhedeal.com

# add to Claude Code
claude mcp add --transport http com-jointhedeal-deals 'https://jointhedeal.com/mcp'
Common questions

What is the JoinTheDeal MCP server?

JoinTheDeal is an MCP server listed in the public MCP registry as com.jointhedeal/deals. Search Southern California home deals and group buys. Read-only, no login. This page covers its hosted endpoint (https://jointhedeal.com/mcp).

Is the JoinTheDeal MCP server safe to use?

JoinTheDeal scores 74 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 JoinTheDeal MCP server expose?

JoinTheDeal exposes 5 tools: search_deals, get_deal, list_categories, search_requests, request_group_deal. Their descriptions and schemas cost roughly 719 tokens of context every time the server is loaded.

Does the JoinTheDeal MCP server require authentication?

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

Is the JoinTheDeal MCP server still maintained?

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

What did VerifyMCP test on the JoinTheDeal MCP server?

VerifyMCP ran 13 checks on JoinTheDeal, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.