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.

PostThisDeal Deal Evidence

REMOTE · POSTTHISDEAL.COM

Deals with their evidence: price, conditions, eligibility, freshness and whether it was checked.

Available components

+3 this week 74 Trust /100

Last scanned (14 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 Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1376 tokens (~172/item across 8 items; 8 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 Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 83% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 0
    • Server version: 1.7.2 → 1.7.4 functional
    • “search_deals” added an optional parameter “fresh_only” cosmetic
    • “search_deals” reworded the description of “verified_only” cosmetic
  • 17 Nov 26 +1
    • Server version: 1.7.1 → 1.7.2 functional
  • 16 Nov 26 0
    • Server version: 1.7.0 → 1.7.1 functional
  • 15 Nov 26 +1
    • Server version: 1.6.0 → 1.7.0 functional
  • 14 Nov 26 0
    • Server version: 1.4.12 → 1.6.0 functional
  • 13 Nov 26 +1

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

  • 11 Nov 26 +1
    • Server version: 1.4.11 → 1.4.12 functional
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://postthisdeal.com/wp-json/ptd-evidence/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=postthisdeal.com CN=YE1,O=Let's Encrypt,C=US 13 Nov 2026 11 Feb 2027 ECDSA 256 ECDSA-SHA384 53a0e695a23fd6742664e8e27ed04193dd8
SANs: postthisdeal.com, www.postthisdeal.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 postthisdeal.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
postthisdeal.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
Header Value
content-security-policy upgrade-insecure-requests
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://postthisdeal.com/wp-json/ptd-evidence/v1/mcp Verified 200
http (plaintext) http://postthisdeal.com/wp-json/ptd-evidence/v1/mcp HTTPS enforced 301 https://postthisdeal.com/wp-json/ptd-evidence/v1/mcp
MCP tools · 8 exposed · ~1,207 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_eligibility ~254

Evaluate whether a shopper can get an offer’s price, given what you know about them: memberships, location, app or store purchase, first order, coupon clipping, Subscribe & Save and order total. Anything not supplied stays unknown and makes the verdict "uncertain" rather than "eligible".

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2 country of delivery.
first_orderboolean–Whether this would be the shopper’s first order at the retailer.
in_storeboolean–Whether the shopper will buy in a store.
membershipsarray–Programmes the shopper holds: amazon_prime, walmart_plus, target_circle_360, target_circle_card, costco_member, sams_club, kohls_rewards, student, store_card. Omit if unknown.
offer_idintegeryesOffer id from search_deals.
order_totalnumber–Expected order total, for minimum-spend conditions.
uses_appboolean–Whether the shopper will buy in the retailer’s app.
will_clipboolean–Whether the shopper will clip an on-page coupon.
will_subscribeboolean–Whether the shopper accepts Subscribe & Save.
NameTypeReqDescription
checksarray––
stepsarray––
summarystring––
verdictstring––

No examples provided.

get_changes ~153

Offers updated, verified or withdrawn since a cursor (or a time). Each change has a category: initial (a first record — not a check), check (a completed check confirmed the price), price_check (a completed check found a different price), availability, freshness, publication (withdrawn, restored, expired), listing (an edit to the listing — stated, not checked). Pass next_cursor back as since to continue.

NameTypeReqDescription
categoriesarray––
kindsarray––
limitinteger––
offer_idinteger–Offer id from search_deals.
sincestring–Cursor from a previous call.
since_timestring–When you have no cursor.
NameTypeReqDescription
changesarray––
has_moreboolean––
next_cursorstring––

No examples provided.

get_comparison ~105

One published comparison: the exact product, every approved offer with its seller, price, stated shipping, known total, evidence status and last automated check, whether the price changed since the editors' review, sourced end dates, and the editorial verdict. last_human_review and last_price_check are separate facts. The lowest known total is named only among the offers PostThisDeal checked; commission is never a ranking input.

NameTypeReqDescription
comparison_idintegeryesFrom search_comparisons.
NameTypeReqDescription
comparison_idinteger––
offersarray––
verdictstring––

No examples provided.

get_offer ~51

The full evidence record for one offer: exact product identity, price and its conditions, the verification ledger, freshness, price context and recent changes.

NameTypeReqDescription
offer_idintegeryesOffer id from search_deals.
NameTypeReqDescription
conditionsobject––
evidenceobject––
freshnessobject––
idinteger––
offerobject––
statusobject––
unknownsarray––

No examples provided.

get_price_context ~72

How the offer’s price compares with independent checks of the same exact product, and how strong that comparison is (coverage: strong, limited or none). Repeat the coverage alongside any conclusion.

NameTypeReqDescription
daysinteger–Window, default 30.
offer_idintegeryesOffer id from search_deals.
NameTypeReqDescription
coveragestring––
observationsinteger––
positionstring––
statementstring––

No examples provided.

search_comparisons ~118

Published price comparisons built and reviewed by PostThisDeal editors: one exact product (model, kit, condition) compared across retailers. Only editor-approved offers are included; unreviewed AI findings never are. Each result has a stable comparison_id for get_comparison.

NameTypeReqDescription
brandstring–Brand name, e.g. Canon.
limitinteger––
querystring–Product words, e.g. "Canon EOS R100".
retailerstring–Retailer name, e.g. Best Buy.
NameTypeReqDescription
comparisonsarray––

No examples provided.

search_deals ~325

Find current offers PostThisDeal tracks that match a need and budget. Results are the best of the offers PostThisDeal tracks, not every store. Each carries its freshness (confirmed, due, overdue or not independently verified), a status block with the separate facts (verification: independent|merchant|none; freshness; availability; price: matched|changed|variable|unknown; publication), conditions and unknowns. Withdrawn offers are never returned. Give memberships to leave out prices the shopper cannot get.

NameTypeReqDescription
categorystring–Category slug.
countrystring–ISO 3166-1 alpha-2 country of delivery.
currencystring–ISO 4217, default USD.
fresh_onlyboolean–Only offers confirmed inside the freshness window right now (use this before calling a price current).
limitinteger––
max_pricenumber–Budget for one item.
membershipsarray–Programmes the shopper holds: amazon_prime, walmart_plus, target_circle_360, target_circle_card, costco_member, sams_club, kohls_rewards, student, store_card. Omit if unknown.
querystring–What the shopper wants, in words that would appear in a product title.
retailerstring–Retailer slug, e.g. walmart, target, amazon.
sortstring––
verified_onlyboolean–Only offers whose price was confirmed at the retailer at some point (the confirmation may be due for a re-check: read freshness.state).
NameTypeReqDescription
notestring––
offersarray––
totalinteger––

No examples provided.

verify_offer ~129

Request a fresh check of the offer at the retailer, and report exactly what could and could not be confirmed. request_status says whether a check was made (completed, attempted_no_result, cached, in_progress, refused); verification_established is true only when a completed check read a price. A failed or unreadable check verifies nothing. A page check confirms a listed price and availability at most — never that a coupon code works. Needs a PostThisDeal agent key; repeated requests for the same offer within minutes return the last result.

NameTypeReqDescription
offer_idintegeryesOffer id from search_deals.
NameTypeReqDescription
attemptedboolean––
confirmedarray––
could_not_confirmarray––
ledger_check_idinteger––
outcomestring––
request_statusstring––
verification_establishedboolean––

No examples provided.

Install

How do I install the PostThisDeal Deal Evidence MCP server?

PostThisDeal Deal Evidence is a hosted endpoint at https://postthisdeal.com/wp-json/ptd-evidence/v1/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 · postthisdeal.com

# add to Claude Code
claude mcp add --transport http com-postthisdeal-deal-evidence 'https://postthisdeal.com/wp-json/ptd-evidence/v1/mcp'
Common questions

What is the PostThisDeal Deal Evidence MCP server?

PostThisDeal Deal Evidence is an MCP server listed in the public MCP registry as com.postthisdeal/deal-evidence. Deals with their evidence: price, conditions, eligibility, freshness and whether it was checked. This page covers its hosted endpoint (https://postthisdeal.com/wp-json/ptd-evidence/v1/mcp).

Is the PostThisDeal Deal Evidence MCP server safe to use?

PostThisDeal Deal Evidence 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 PostThisDeal Deal Evidence MCP server expose?

PostThisDeal Deal Evidence exposes 8 tools: search_deals, get_offer, check_eligibility, verify_offer, get_price_context, and 3 more. Their descriptions and schemas cost roughly 1,207 tokens of context every time the server is loaded.

Does the PostThisDeal Deal Evidence MCP server require authentication?

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

Is the PostThisDeal Deal Evidence MCP server still maintained?

PostThisDeal Deal Evidence 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 PostThisDeal Deal Evidence MCP server?

VerifyMCP ran 13 checks on PostThisDeal Deal Evidence, 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.