_ registry / mcp streamable-http · checked 54m ago

Espresso Steals

listed under this name in a public catalogue; the server gives only its address, espressosteals.com

https://espressosteals.com

Registry code: 7252523a591201e8

api record

Espresso Steals tracks espresso gear on Amazon: daily prices, 2+ years of history, and a BUY call when a product is at a genuine low, computed from its own history (never list prices); otherwise no call, and no prediction. Use list_slots to learn the parts of a setup, search_catalog to find candidates (filter by slot, words, price band, brand, on-sale), and get_product for sentiment, sizing and links before recommending. search_catalog always answers: products it can price, known_unpriced for gear it knows but cannot price (sold direct by the maker, such as Niche, Lelit or Decent: say so and…

endpoint
https://espressosteals.com/api/mcp
protocol
streamable-http ·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 Espresso Steals live?
Yes — it answered the hub's last check (checked 54m ago). It answered 99% of checks over the last 30 days.
Is Espresso Steals free to use?
Yes — the hub reached it with no key and no payment.
What tools does Espresso Steals have?
4 tools: get_product, watch_price, search_catalog, list_slots.
Is Espresso Steals 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.4%

90 days 99.7%· all time 99.7%

latency
574ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 303 checks · signed record
  • degraded → live
  • live → degraded· HTTP 521
  • degraded → live
  • unknown → live
_ what it is for
used for
  • search espresso gear with price history
  • get product detail and buy signal
  • list parts of an espresso setup
  • set a price drop email alert
takes → gives
text → data
tools
3 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 4 tools
2 open 2 never probed 2 of 4 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.

  • search_catalog reads open 54m ago

    Search the espresso gear this site tracks. `products` have a live Amazon price and, when at a genuine low, a BUY call computed from their own price history; otherwise no call. Filter by slot (the role a product plays in a setup), free-text words (brand and model names, partial words and small typos are fine), a price band, a brand, or on-sale only. Products we know but cannot price (sold direct by the maker, e.g. Niche, Lelit, Decent) come back in `known_unpriced` with no price and the reason: say so, quote the note, and link the url. When nothing in `products` matches, `alternatives` lists the closest tracked products with live prices and `note` says what was and was not found. Never tell the user the site has nothing; tell them what it has.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "slot": {
          "enum": [
            "machine",
            "grinder",
            "scale",
            "tamper",
            "water",
            "cleaning",
            "pitcher",
            "wdt",
            "funnel",
            "puckscreen",
            "basket",
            "knockbox",
            "mat"
          ],
          "type": "string",
          "description": "Restrict to one slot. Omit to search every slot."
        },
        "brand": {
          "type": "string",
          "description": "Only this brand (case-insensitive; \"Niche Coffee\" finds Niche)."
        },
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Max results. Default 12."
        },
        "query": {
          "type": "string",
          "description": "Free-text words to match (any word matches; names and brands rank first), e.g. \"niche\", \"bambino plus\", \"hand burr\", \"dual boiler\"."
        },
        "max_price": {
          "type": "number",
          "description": "Only products at or under this USD price."
        },
        "min_price": {
          "type": "number",
          "description": "Only products at or over this USD price."
        },
        "on_sale_only": {
          "type": "boolean",
          "description": "Only products at a good price today (verdict = buy)."
        }
      }
    }
    arguments 50 lines
  • list_slots reads open 54m ago

    The slots an espresso setup is built from (machine, grinder, scale, tamper…), with what each is for. Use the ids as search_catalog's `slot`.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_product reads unknown 54m ago

    Full detail for one product by slug: community sentiment, reference price and basis, date of the latest price observation, portafilter size (machines) or accessory size (sized accessories), superautomatic / manual-lever / hand-grinder flags, product URL and Amazon link. A known product with no price returns price null, the reason, and priced alternatives. An unknown slug returns did_you_mean.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "A slug from search_catalog (products or known_unpriced)."
        }
      }
    }
    arguments 12 lines
  • watch_price changes data unknown never probed

    Email the user when a product is at a good price (a verified low), or at or under a target price they name. Use after search_catalog/get_product when the user wants to be told when to buy. Ask the user for their email; never invent or reuse one. One watch per email per product; calling again updates the target. The first time an address is used it receives a confirmation email and the watch arms when they click it — tell the user to check their inbox. Each alert links to the product page and carries an unsubscribe link.

    mcp-tool

    {
      "type": "object",
      "required": [
        "email",
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "A slug from search_catalog or get_product."
        },
        "email": {
          "type": "string",
          "description": "The user's email address, given by the user in this conversation."
        },
        "target_price": {
          "type": "number",
          "description": "Optional USD price to alert at or under. Omit to alert on the next verified low."
        }
      }
    }
    arguments 21 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 7252523a591201e8.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/7252523a591201e8/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/7252523a591201e8/badge.svg)](https://brick.blue/agent/7252523a591201e8?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
80%

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.