_ registry / mcp streamable-http · checked 2h ago

buywise

https://api.buywise.fyi

Registry code: c63d7e2302bc463d

api record

BuyWise gives shopping trust signals: findings on a brand or an online store's product listing, each with a confidence. The tools never browse the web, so pass the listing details already in the conversation. One check_brands or check_products call covers several brands or listings at once. Findings are signals for the user to weigh, never a buy or avoid verdict.

endpoint
https://api.buywise.fyi/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 buywise live?
Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
Is buywise free to use?
Yes — the hub reached it with no key and no payment.
What tools does buywise have?
3 tools: check_product, check_products, check_brands.
Is buywise 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
97.6%

90 days 97.9%· all time 97.9%

latency
239ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 96 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 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.

  • check_product unknown 2h ago

    Use this when the user is looking at a specific product listing on an online store and wants to know whether it looks trustworthy or like a good buy. Pass what you already read from the listing as arguments: title (required) and, when shown, brand, price, listPrice (the seller's "was" price), currency, url, seller, category, rating, reviewCount and key details; each extra field sharpens the read. Returns findings such as generic white-label product, quality, price, questionable discount, review credibility and seller legitimacy, each with a confidence, plus a report on the brand unless includeBrand is false. Signals only, never a buy or avoid verdict. Does not browse: only the domain of url is used. Not for banking, health, government or email pages.

    mcp-tool

    {
      "type": "object",
      "required": [
        "title"
      ],
      "properties": {
        "id": {
          "type": "string",
          "maxLength": 100,
          "description": "Your own id for this product (e.g. an ASIN or list index); echoed back."
        },
        "url": {
          "type": "string",
          "maxLength": 2048,
          "description": "Listing URL. Only its domain is used."
        },
        "brand": {
          "type": "string",
          "maxLength": 200,
          "description": "Brand or maker, if the listing names one."
        },
        "price": {
          "type": "number",
          "maximum": 10000000,
          "minimum": 0,
          "description": "What the buyer would pay now, as a number."
        },
        "title": {
          "type": "string",
          "maxLength": 1000,
          "minLength": 1,
          "description": "Product title exactly as the listing shows it."
        },
        "detail": {
          "type": "boolean",
          "description": "Include each finding's full probability distribution. Default false."
        },
        "rating": {
          "type": "number",
          "maximum": 5,
          "minimum": 0,
          "description": "Average star rating out of 5."
        },
        "seller": {
          "type": "string",
          "maxLength": 300,
          "description": "Seller or store name, if different from the site."
        },
        "details": {
          "type": "string",
          "maxLength": 20000,
          "description": "Key specs or bullet points as plain text. Longer text is trimmed."
        },
        "category": {
          "type": "string",
          "maxLength": 300,
          "description": "Product category, e.g. \"Headphones\"."
        },
        "currency": {
          "type": "string",
          "pattern": "^[A-Za-z]{3}$",
          "description": "ISO 4217 code for price and listPrice. Default USD."
        },
        "listPrice": {
          "type": "number",
          "maximum": 10000000,
          "minimum": 0,
          "description": "The seller's \"was\" / \"list\" / \"typical\" price, if shown."
        },
        "reviewCount": {
          "type": "integer",
          "maximum": 1000000000,
          "minimum": 0,
          "description": "Number of ratings or reviews."
        },
        "includeBrand": {
          "type": "boolean",
          "description": "Also report on the brand the listing names (its brand field), with findings on the brand itself. Default true."
        }
      }
    }
    arguments 81 lines
  • check_products unknown 2h ago

    Use this when the user is comparing several product listings, such as search results or the same item at different stores, and wants trust signals on each. Pass up to 20 products, each with what you already read from its listing: title (required) and, when shown, brand, price, listPrice, currency, url, seller, category, rating, reviewCount, details, plus your own id to match results. Returns, in input order, the same findings as check_product for each; a product that can't be checked carries an error and message instead. Signals only, never a buy or avoid verdict. Does not browse the web. Not for banking, health, government or email pages.

    mcp-tool

    {
      "type": "object",
      "required": [
        "products"
      ],
      "properties": {
        "detail": {
          "type": "boolean",
          "description": "Include each finding's full probability distribution. Default false."
        },
        "products": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "title"
            ],
            "properties": {
              "id": {
                "type": "string",
                "maxLength": 100,
                "description": "Your own id for this product (e.g. an ASIN or list index); echoed back."
              },
              "url": {
                "type": "string",
                "maxLength": 2048,
                "description": "Listing URL. Only its domain is used."
              },
              "brand": {
                "type": "string",
                "maxLength": 200,
                "description": "Brand or maker, if the listing names one."
              },
              "price": {
                "type": "number",
                "maximum": 10000000,
                "minimum": 0,
                "description": "What the buyer would pay now, as a number."
              },
              "title": {
                "type": "string",
                "maxLength": 1000,
                "minLength": 1,
                "description": "Product title exactly as the listing shows it."
              },
              "rating": {
                "type": "number",
                "maximum": 5,
                "minimum": 0,
                "description": "Average star rating out of 5."
              },
              "seller": {
                "type": "string",
                "maxLength": 300,
                "description": "Seller or store name, if different from the site."
              },
              "details": {
                "type": "string",
                "maxLength": 20000,
                "description": "Key specs or bullet points as plain text. Longer text is trimmed."
              },
              "category": {
                "type": "string",
                "maxLength": 300,
                "description": "Product category, e.g. \"Headphones\"."
              },
              "currency": {
                "type": "string",
                "pattern": "^[A-Za-z]{3}$",
                "description": "ISO 4217 code for price and listPrice. Default USD."
              },
              "listPrice": {
                "type": "number",
                "maximum": 10000000,
                "minimum": 0,
                "description": "The seller's \"was\" / \"list\" / \"typical\" price, if shown."
              },
              "reviewCount": {
                "type": "integer",
                "maximum": 1000000000,
                "minimum": 0,
                "description": "Number of ratings or reviews."
              }
            },
            "description": "A product as seen on a store listing. Only title is required; each extra field sharpens the read."
          },
          "maxItems": 20,
          "minItems": 1,
          "description": "Products, 1-20."
        },
        "includeBrand": {
          "type": "boolean",
          "description": "Also report on the brand the listing names (its brand field), with findings on the brand itself. Default true."
        }
      }
    }
    arguments 96 lines
  • check_brands unknown 2h ago

    Use this when the user asks whether a brand is reputable or what kind of brand it is (an established name, a store's own label, an independent maker, or a generic white-label name), or wants brands compared while shopping. Returns findings on each brand: what kind of brand it is, its reputation for quality and its usual price tier, each with a confidence. Signals only, never a buy or avoid verdict. Does not browse the web and is not for banking, health or email pages. Pass brand names as the user or the listing gave them, up to 50 per call.

    mcp-tool

    {
      "type": "object",
      "required": [
        "brands"
      ],
      "properties": {
        "brands": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 200,
            "minLength": 1
          },
          "maxItems": 50,
          "minItems": 1,
          "description": "Brand names, 1-50."
        },
        "detail": {
          "type": "boolean",
          "description": "Include each finding's full probability distribution. Default false."
        }
      }
    }
    arguments 23 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 c63d7e2302bc463d.

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

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.