MasaDeals MCP server
io.github.MKagesawa/masadealsMKagesawastreamable-httpv0.1.3Scanned
Verified promo codes and savings facts for shopping agents — ranked by checkout success only.
3 tools: 2 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the MasaDeals MCP server can do
The MasaDeals MCP server is published by the GitHub account MKagesawa. It has 3 tools. It can create or change data (2 tools: check_code and report_outcome), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 4 times since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 0.1.3.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 2Claude Code: ask
check_codeCheck one specific code: status (verified/declared/stale/dead/unknown_code), structured constraints, success stats, and — if a cart is supplied — whether it would apply.1 finding
Why it is in this group
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "check_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHintJustification: Read-only: the call only reads the stored record for one code — its status, constraints, and success stats — and returns it; it creates, changes, and deletes nothing.
- destructiveHintJustification: Not destructive: checking a code cannot delete, overwrite, or irreversibly change any data, account, order, or external state.
- openWorldHintJustification: Not open-world: the answer comes only from MasaDeals' own bounded, checkout-tested dataset — the tool performs no web search or browsing and reaches no arbitrary external system.
report_outcomeReport what happened when a code was tried at checkout.No findings
Why it is in this group
- The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it Report what happened when a code was tried at checkout. This telemetry is what keeps the feed verified — free-tier callers must report outcomes.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHintJustification: Not read-only: the call appends one checkout-outcome event to MasaDeals' own telemetry store, updating the code's success statistics — that is why readOnlyHint is false. It is also not idempotent: eac… [67 more characters not shown]
- destructiveHintJustification: Not destructive: recording an outcome only appends telemetry — it never deletes or overwrites existing records, and it changes nothing at any merchant (no orders, accounts, payments, or cancellations)… [1 more characters not shown]
- openWorldHintJustification: Not open-world: the write goes only to MasaDeals' own telemetry store; the tool contacts no external system and takes no action on the public internet.
Only reads 1Show 1 read-only tool
find_codesFind promo codes that fit this cart, ranked by verified checkout success only.No findings
Why it is in this group
- The name "find_codes" says "find": a word for reading.
Description, as the server wrote it Find promo codes that fit this cart, ranked by verified checkout success only. Coverage (Nov 16, 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. 180 codes tested; 7 currently verified across Adidas, Chewy, and Home Depot. 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 (77 facts: shipping thresholds, membership discounts, price-match policies, live sales), served in merchant detail responses. Merchants outside the covered set return 'merchant_not_found'.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHintJustification: Read-only: the call only looks up promo codes already held in the MasaDeals dataset and returns them; it creates, changes, and deletes nothing.
- destructiveHintJustification: Not destructive: a lookup cannot delete, overwrite, or irreversibly change any data, account, order, or external state.
- openWorldHintJustification: Not open-world: answers come only from MasaDeals' own bounded, checkout-tested dataset for named merchants — the tool performs no web search or browsing and reaches no arbitrary external system.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 16, 2026, 14:22 UTC, unchanged since Nov 2, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://masadeals.com/mcp: tools/list returned 3 tools to an anonymous client, including check_code (write), report_outcome (write)
Findings
Matches of fixed checks, with the text they matched.
- Warncheck_code
The server marks "check_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:find_codesOnly readsdescription
Tools1 changed.~1 changedView diff
- Changed:report_outcomeChanges thingsannotations
Tools1 changed.~1 changedView diff
- Changed:find_codesOnly readsdescription
Tools3 changed.~3 changedView diff
- Changed:check_codeChanges thingsinputSchemaannotations
- Changed:find_codesOnly readsinputSchemaannotations
- Changed:report_outcomeChanges thingsinputSchemaannotations
Install
Pinned to version 0.1.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http masadeals https://masadeals.com/mcpclaude mcp add --transport http masadeals https://masadeals.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__masadeals__find_codes"
],
"ask": [
"mcp__masadeals__check_code",
"mcp__masadeals__report_outcome"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as masadeals. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.MKagesawa/masadeals/verify?hash=7d7702203b7c632f68e7ac7d04a11ac619f7ea958424aa1d5cc7150cabad17b6" | jq -e '.changed == false'Pinned hash 7d7702203b7c, from Nov 16, 2026, 15:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.MKagesawa/masadeals/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.MKagesawa/masadeals)Source: MCP Registry · repository. Synced Nov 16, 2026, 16:17 UTC.
MasaDeals MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the MasaDeals MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the MasaDeals MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the MasaDeals MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the MasaDeals MCP server have?
- 3 tools: 2 write, 1 read. check_code, report_outcome and find_codes.
Does the MasaDeals MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the MasaDeals MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the MasaDeals MCP server changed its tools?
- Yes, 4 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.