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.

MasaDeals

REMOTE · MASADEALS.COM

Verified promo codes and savings facts for shopping agents — ranked by checkout success only.

Available components

+2 this week 73 Trust /100

Last scanned (19 hours ago)

Scores higher than 59% 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 Security63
  • 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • 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 Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 477 tokens (~159/item across 3 items; 3 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 Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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 0
    • Tool “find_codes” rewrote its description, which is the text the model reads security
  • 20 Nov 26 +1
    • Tool “find_codes” rewrote its description, which is the text the model reads security
  • 19 Nov 26 0
    • Tool “find_codes” rewrote its description, which is the text the model reads security
  • 18 Nov 26 0
    • Tool “find_codes” rewrote its description, which is the text the model reads security
  • 17 Nov 26 +1

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

  • 16 Nov 26 −1
    • Tool “find_codes” rewrote its description, which is the text the model reads security
    • Schema quality: 134 → 155 ▼ functional
    • Server version: 0.1.1 → 0.1.3 functional
    • Tool “check_code” changed its title: Check Code cosmetic
    • Tool “find_codes” changed its title: Find Codes cosmetic
    • Tool “report_outcome” changed its title: Report Outcome cosmetic
  • 15 Nov 26 +1

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

  • 13 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.

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

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=masadeals.com CN=WE1,O=Google Trust Services,C=US 31 Oct 2026 29 Jan 2027 ECDSA 256 ECDSA-SHA256 9192f8c9fe753a1713fd6ea53e6a9c29
SANs: masadeals.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of masadeals.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
masadeals.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://masadeals.com/mcp Verified 200
http (plaintext) http://masadeals.com/mcp Inconclusive 405
MCP tools · 3 exposed · ~477 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
check_code ~108

Check one specific code: status (verified/declared/stale/dead/unknown_code), structured constraints, success stats, and — if a cart is supplied — whether it would apply.

NameTypeReqDescription
cartobject–Optional cart context — when supplied, the answer includes whether the code would apply to this cart
codestringyesThe promo code to check, exactly as a shopper would enter it at checkout
merchantstringyesMerchant slug, e.g. 'nike'

No output schema declared.

No examples provided.

find_codes ~241

Find promo codes that fit this cart, ranked by verified checkout success only. Coverage (Nov 20, 2026): live guest-cart test results for 20 merchants — Adidas, Best Buy, Chewy, CVS Photo, Dick's Sporting Goods, Fanatics, Home Depot, Kohl's, Macy's, Michaels, Nike, Nordstrom, Sephora, Staples, Target, Ulta Beauty, Under Armour, Walmart, Wayfair, Zappos. 235 codes tested; 14 currently verified across Adidas, Chewy, Home Depot, Kohl's, Michaels, Staples, and CVS Photo. For a covered merchant with no working code, the verdict is 'no_verified_code' with that merchant's dated test record — a certified negative. The service also holds merchant-published savings facts for the same 20 merchants (84 facts: shipping thresholds, membership discounts, price-match policies, live sales), served in merchant detail responses. Merchants outside the covered set return 'merchant_not_found'.

NameTypeReqDescription
cartobject–The actual cart context — constraints are checked against it
merchantstringyesMerchant slug, e.g. 'nike'

No output schema declared.

No examples provided.

report_outcome ~128

Report what happened when a code was tried at checkout. This telemetry is what keeps the feed verified — free-tier callers must report outcomes.

NameTypeReqDescription
appliedbooleanyestrue if the code applied successfully
codestringyesThe promo code that was tried at checkout
failure_reasonstring–Why the code did not apply (report when applied is false): expired, min_not_met, geo, category, customer_type, not_stackable, single_use_exhausted, code_rejected, other
merchantstringyesMerchant slug, e.g. 'nike'

No output schema declared.

No examples provided.

Install

How do I install the MasaDeals MCP server?

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

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

What is the MasaDeals MCP server?

MasaDeals is an MCP server listed in the public MCP registry as io.github.MKagesawa/masadeals. Verified promo codes and savings facts for shopping agents, ranked by checkout success only. This page covers its hosted endpoint (https://masadeals.com/mcp).

Is the MasaDeals MCP server safe to use?

MasaDeals scores 73 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 MasaDeals MCP server expose?

MasaDeals exposes 3 tools: find_codes, check_code, report_outcome. Their descriptions and schemas cost roughly 477 tokens of context every time the server is loaded.

Does the MasaDeals MCP server require authentication?

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

Is the MasaDeals MCP server still maintained?

MasaDeals 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 MasaDeals MCP server?

VerifyMCP ran 12 checks on MasaDeals, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about MasaDeals: HTTPS. 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.