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.

PriceTrack

REMOTE · PRICETRACK.DEV · 2 COMPONENTS · SCANNED SEP 20

Live SaaS pricing: current plans, verified price changes, and comparisons for 33,000+ products.

+2 this week 80 Trust /100
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
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 558 tokens (~69/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 71% 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
  • 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 8 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
Install

How do I install the PriceTrack MCP server?

PriceTrack is a hosted endpoint at https://pricetrack.dev/api/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 · pricetrack.dev

# add to Claude Code
claude mcp add --transport http dev-pricetrack-pricetrack 'https://pricetrack.dev/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-pricetrack-pricetrack": {
      "url": "https://pricetrack.dev/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-pricetrack-pricetrack": {
      "type": "http",
      "url": "https://pricetrack.dev/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.dev-pricetrack-pricetrack]
url = "https://pricetrack.dev/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-pricetrack-pricetrack": {
      "type": "remote",
      "url": "https://pricetrack.dev/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-pricetrack-pricetrack --url 'https://pricetrack.dev/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dev-pricetrack-pricetrack:
    url: "https://pricetrack.dev/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-pricetrack-pricetrack": {
      "Transport": "http",
      "Url": "https://pricetrack.dev/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add dev-pricetrack-pricetrack -t streamable-http -u 'https://pricetrack.dev/api/mcp'
// mcp.json
{
  "mcpServers": {
    "dev-pricetrack-pricetrack": {
      "type": "http",
      "url": "https://pricetrack.dev/api/mcp"
    }
  }
}

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

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.

  • 18 Sept 26 0
    • Stability: 0.97 → pass security
  • 17 Sept 26 +1

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

  • 15 Sept 26 +1

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

  • 13 Sept 26 +1

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

  • 11 Sept 26 +1

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

  • 9 Sept 26 +1

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

  • 7 Sept 26 +1

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

  • 4 Sept 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.

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 20 Sept 2026 · Probed https://pricetrack.dev/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=pricetrack.dev CN=YR2,O=Let's Encrypt,C=US 29 Jul 2026 27 Oct 2026 RSA 2048 SHA256-RSA 6ab2f319d9d4808ebc387f07a2f78891c91
SANs: pricetrack.dev
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of pricetrack.dev. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
pricetrack.dev. absent 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=63072000
content-security-policy frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), interest-cohort=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pricetrack.dev/api/mcp Verified 200
http (plaintext) http://pricetrack.dev/api/mcp HTTPS enforced 308 https://pricetrack.dev/api/mcp
MCP tools · 8 exposed · ~558 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
compare_products ~70

Compare the current pricing plans of 2 to 5 SaaS products side by side. Call this when the user is choosing between named products and wants their prices in one view. Takes product slugs (find them with search_products).

NameTypeReqDescription
slugsarrayyes2-5 product slugs

No output schema declared.

No examples provided.

create_price_alert ~96

Create an email alert on a product's price for the signed-in user. Fires when the product's price changes (any_change) or moves by at least a threshold percentage. This modifies the user's account — only call when they explicitly ask to be alerted or to watch a product's price.

NameTypeReqDescription
slugstringyes
thresholdPercentageintegerOnly alert on moves of at least this percent; omit for any change

No output schema declared.

No examples provided.

get_price_history ~80

The complete verified price-change history of a product, beyond the public 10-change window. Requires the user's PriceTrack account. Call when the user asks how a product's price evolved over time, or for changes older than the recent ones get_product shows.

NameTypeReqDescription
limitintegerMax changes, default 100
slugstringyes

No output schema declared.

No examples provided.

get_product ~93

Get a SaaS product's current pricing plans and its most recent price changes. Call this when the user asks what a specific product costs, what plans it offers, or whether its price changed recently. Takes the product slug (find it with search_products). Shows the 10 most recent changes; deeper history requires a free PriceTrack API key.

NameTypeReqDescription
slugstringyesProduct slug, e.g. "notion"

No output schema declared.

No examples provided.

get_stack ~32

The products the signed-in user tracks on PriceTrack, with each one's current lowest paid price and an estimated monthly total.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_alerts ~22

The user's active price alerts on PriceTrack. Requires their account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

recent_price_changes ~73

The most recent verified SaaS price changes and the biggest movers of the last 30 days, across the whole catalogue. Call this when the user asks what changed in SaaS pricing lately, who raised prices recently, or for examples of price increases. Fixed snapshot of up to 25 entries per group — no pagination.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_products ~92

Search PriceTrack's catalogue of tracked SaaS products by name or description. Call this when the user asks what a SaaS product costs and you need its slug, or when they describe a kind of tool and want priced options. Returns up to 20 matches with slug, category, and starting price. Use get_product with a returned slug for full plan details.

NameTypeReqDescription
querystringyesProduct name or keywords

No output schema declared.

No examples provided.

Common questions

What is the PriceTrack MCP server?

PriceTrack is an MCP server listed in the public MCP registry as dev.pricetrack/pricetrack. Live SaaS pricing: current plans, verified price changes, and comparisons for 33,000+ products. This page covers its hosted endpoint (https://pricetrack.dev/api/mcp).

Is the PriceTrack MCP server safe to use?

PriceTrack scores 80 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 PriceTrack MCP server expose?

PriceTrack exposes 8 tools: search_products, get_product, recent_price_changes, compare_products, get_price_history, and 3 more. Their descriptions and schemas cost roughly 558 tokens of context every time the server is loaded.

Does the PriceTrack MCP server require authentication?

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

Is the PriceTrack MCP server still maintained?

PriceTrack is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.