Prickelly
REMOTE · API.PRICKELLY.APP
Track the price you actually pay on Amazon.com.tr, Hepsiburada and Trendyol.
Available components
Last scanned (14 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
Recent critical change
Authorization (12 Nov 2026). See the changelog before you install this server.
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
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (remove_watch). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 828 tokens (~138/item across 6 items; 6 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 Management33
- Stability observed for 10 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
- 86% 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 7 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
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 →
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 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 18 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.
- 16 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.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 0
- “add_watch” reworded the description of “lang” cosmetic
- “get_deals” reworded the description of “lang” cosmetic
- “get_price_history” reworded the description of “lang” cosmetic
- “list_watches” reworded the description of “lang” cosmetic
- “remove_watch” reworded the description of “lang” cosmetic
- “search_products” reworded the description of “lang” cosmetic
6 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 12 Nov 26 +2
- Authorization: unverified → fail ▼ critical
- The server rewrote its instructions, which are the text every model session reads security
- Tool “remove_watch” is now declared destructive security
- Stability: unverified → 0.03 ▲ functional
- Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- Tool “add_watch” changed its title: Add a watch cosmetic
- Tool “get_deals” changed its title: Get deals cosmetic
- Tool “get_price_history” changed its title: Get price history cosmetic
- Tool “list_watches” changed its title: List watches cosmetic
- Tool “remove_watch” changed its title: Remove a watch cosmetic
- Tool “search_products” changed its title: Search products cosmetic
- 11 Nov 26 63
First indexed and scored.
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://api.prickelly.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=prickelly.app | CN=YE1,O=Let's Encrypt,C=US | 9 Nov 2026 | 7 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6dde8ea2f9f3947cc1f9e30ea13b273f840 |
| SANs: *.prickelly.app, prickelly.app | ||||||
| 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 api.prickelly.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| prickelly.app. | 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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.prickelly.app/mcp | Verified | 200 | |
| http (plaintext) | http://api.prickelly.app/mcp | HTTPS enforced | 308 | https://api.prickelly.app/mcp |
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 →
add_watch Add a watch ~167
Start watching a product for the signed-in user (product URL or id, optional target price). Sends a confirmation email; this tool does not confirm it. Requires a Bearer API key or session token.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Output language: "en" or "tr". Defaults to the user's language when the client says it, otherwise English. |
| marketplace | string | – | – |
| product | string | – | Product id or shop URL to watch. |
| productId | string | – | Product id to watch. |
| query | string | – | A name to search if you do not have a link yet. |
| targetPrice | number | – | Optional target price in TRY. |
| target_price | number | – | Alias of targetPrice. |
| url | string | – | Product URL to watch. |
No output schema declared.
No examples provided.
get_deals Get deals ~130
List current real price drops from the same source as the Prickelly deals page (last 7 days). Optional marketplace filter. No sign-in required.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category name. Not yet used for filtering; included for forward compatibility. |
| lang | string | – | Output language: "en" or "tr". Defaults to the user's language when the client says it, otherwise English. |
| limit | integer | – | Max results, 1-20, default 8. |
| marketplace | string | – | Optional marketplace: amazon_tr, hepsiburada, or trendyol. |
No output schema declared.
No examples provided.
get_price_history Get price history ~195
Get price history for one product (by Prickelly or shop product id, or a product URL). Returns recent points, min, max, current, and a short verdict based only on that history. No sign-in required.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | History window in days, default 90, max 365. |
| lang | string | – | Output language: "en" or "tr". Defaults to the user's language when the client says it, otherwise English. |
| marketplace | string | – | Optional marketplace when only a product id is given. |
| product | string | – | Product id or shop / Prickelly history URL. |
| productId | string | – | Product id, for example HBCV00008O0L2Z or an Amazon ASIN. |
| url | string | – | Product URL from Amazon.com.tr, Hepsiburada, Trendyol, or a Prickelly history link. |
No output schema declared.
No examples provided.
list_watches List watches ~57
List the signed-in user's watched products. Requires a Bearer API key or session token.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Output language: "en" or "tr". Defaults to the user's language when the client says it, otherwise English. |
No output schema declared.
No examples provided.
remove_watch Remove a watch ~101
Remove one of the signed-in user's watches, by watch id or product URL/id. Requires a Bearer API key or session token.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Watch id returned by list_watches. |
| lang | string | – | Output language: "en" or "tr". Defaults to the user's language when the client says it, otherwise English. |
| marketplace | string | – | – |
| productId | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
search_products Search products ~137
Search the Prickelly catalog for products on Amazon.com.tr, Hepsiburada or Trendyol. Returns the current price, marketplace, shop URL and Prickelly history link. No sign-in required.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Output language: "en" or "tr". Defaults to the user's language when the client says it, otherwise English. |
| limit | integer | – | Max results, 1-20, default 8. |
| marketplace | string | – | Optional marketplace: amazon_tr, hepsiburada, or trendyol. |
| query | string | yes | Search text, for example a product name or brand. |
No output schema declared.
No examples provided.
How do I install the Prickelly MCP server?
Prickelly is a hosted endpoint at https://api.prickelly.app/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 · api.prickelly.app
claude mcp add --transport http app-prickelly-tracker 'https://api.prickelly.app/mcp'
What is the Prickelly MCP server?
Prickelly is an MCP server listed in the public MCP registry as app.prickelly/tracker. Track the price you actually pay on Amazon.com.tr, Hepsiburada and Trendyol. This page covers its hosted endpoint (https://api.prickelly.app/mcp).
Is the Prickelly MCP server safe to use?
Prickelly scores 69 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 Prickelly MCP server expose?
Prickelly exposes 6 tools: search_products, get_price_history, get_deals, add_watch, list_watches, remove_watch. Their descriptions and schemas cost roughly 787 tokens of context every time the server is loaded.
Does the Prickelly MCP server require authentication?
No. We connected to Prickelly without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Prickelly MCP server still maintained?
Prickelly 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 Prickelly MCP server?
VerifyMCP ran 13 checks on Prickelly, 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.