# Prickelly (remote · api.prickelly.app)

Track the price you actually pay on Amazon.com.tr, Hepsiburada and Trendyol.

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

> **Recent critical change**: Authorization (2026-11-12). See the changelog below before you install this server.

## Components

- remote · `api.prickelly.app`: 69/100 (this document), [markdown](https://verifymcp.io/servers/app-prickelly-tracker/api.md), [page](https://verifymcp.io/servers/app-prickelly-tracker/api)

## Channel facts

- Endpoint: `https://api.prickelly.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (remove_watch).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http app-prickelly-tracker 'https://api.prickelly.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-prickelly-tracker": {
      "url": "https://api.prickelly.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-prickelly-tracker": {
      "type": "http",
      "url": "https://api.prickelly.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-prickelly-tracker]
url = "https://api.prickelly.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-prickelly-tracker": {
      "type": "remote",
      "url": "https://api.prickelly.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-prickelly-tracker --url 'https://api.prickelly.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-prickelly-tracker:
    url: "https://api.prickelly.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-prickelly-tracker": {
      "Transport": "http",
      "Url": "https://api.prickelly.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-prickelly-tracker -t streamable-http -u 'https://api.prickelly.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-prickelly-tracker": {
      "type": "http",
      "url": "https://api.prickelly.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 69, +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.

### 2026-11-18 (score 68, +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.

### 2026-11-16 (score 67, +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.

### 2026-11-14 (score 66, +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.

### 2026-11-13 (score 65, 0)

- [cosmetic] “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”

### 2026-11-12 (score 65, +2)

- [critical regression] Authorization: unverified → fail
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “remove_watch” is now declared destructive
- [functional improvement] Stability: unverified → 0.03
- [functional] Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
- [cosmetic] 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

### 2026-11-11 (score 63)

First indexed and scored.

## MCP tools (6)

### `search_products` (~137 tokens)

Search products

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.

Input parameters:

- `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, required): Search text, for example a product name or brand.

### `get_price_history` (~195 tokens)

Get price history

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.

Input parameters:

- `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.

### `get_deals` (~130 tokens)

Get deals

List current real price drops from the same source as the Prickelly deals page (last 7 days). Optional marketplace filter. No sign-in required.

Input parameters:

- `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.

### `add_watch` (~167 tokens)

Add a watch

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.

Input parameters:

- `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.

### `list_watches` (~57 tokens)

List watches

List the signed-in user's watched products. Requires a Bearer API key or session token.

Input parameters:

- `lang` (string): Output language: "en" or "tr". Defaults to the user's language when the client says it, otherwise English.

### `remove_watch` (~101 tokens)

Remove a watch

Remove one of the signed-in user's watches, by watch id or product URL/id. Requires a Bearer API key or session token.

Input parameters:

- `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)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-prickelly-tracker/api#diagnostics

## Score history

- 2026-11-21: 69
- 2026-11-20: 69
- 2026-11-19: 68
- 2026-11-18: 68
- 2026-11-17: 67
- 2026-11-16: 67
- 2026-11-15: 66
- 2026-11-14: 66
- 2026-11-13: 65
- 2026-11-12: 65
- 2026-11-11: 63

## Common questions

### 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.

## Links

- Remote endpoint: https://api.prickelly.app/mcp
- Repository: https://github.com/ozulkuomer/prickelly
- Website: https://prickelly.app/mcp
- Changelog RSS feed: https://verifymcp.io/servers/app-prickelly-tracker/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-prickelly-tracker/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-prickelly-tracker/api.json
- HTML version of this page: https://verifymcp.io/servers/app-prickelly-tracker/api
