_ registry / mcp http-sse · checked 29m ago

pricetrack

https://pricetrack.dev

Registry code: 51aea5f89d50105f

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://pricetrack.dev/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is pricetrack live?
Yes — it answered the hub's last check (checked 29m ago). It answered 99% of checks over the last 30 days.
Is pricetrack free to use?
Yes — the hub reached it with no key and no payment.
What tools does pricetrack have?
8 tools: get_product, search_products, compare_products, get_price_history, list_alerts, create_price_alert, get_stack, recent_price_changes.
Is pricetrack safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.3%

90 days 99.5%· all time 99.5%

latency
277ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 400 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • get current saas pricing plans
  • compare saas product prices
  • see recent saas price changes
  • create a price change alert
takes → gives
text → data
tools
7 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
1 open 7 never probed 1 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • recent_price_changes reads open 7h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • get_product reads unknown 14h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 255,
          "minLength": 1,
          "description": "Product slug, e.g. \"notion\""
        }
      }
    }
    arguments 15 lines
  • search_products reads unknown 29m ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Product name or keywords"
        }
      }
    }
    arguments 15 lines
  • compare_products reads unknown 14h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "slugs"
      ],
      "properties": {
        "slugs": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 255,
            "minLength": 1
          },
          "maxItems": 5,
          "minItems": 2,
          "description": "2-5 product slugs"
        }
      }
    }
    arguments 20 lines
  • get_price_history reads unknown 14h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 255,
          "minLength": 1
        },
        "limit": {
          "type": "integer",
          "maximum": 500,
          "minimum": 1,
          "description": "Max changes, default 100"
        }
      }
    }
    arguments 20 lines
  • list_alerts reads unknown 7h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • create_price_alert changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 255,
          "minLength": 1
        },
        "thresholdPercentage": {
          "type": "integer",
          "maximum": 95,
          "minimum": 1,
          "description": "Only alert on moves of at least this percent; omit for any change"
        }
      }
    }
    arguments 20 lines
  • get_stack reads unknown 7h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 51aea5f89d50105f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/51aea5f89d50105f/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/51aea5f89d50105f/badge.svg)](https://brick.blue/agent/51aea5f89d50105f?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.