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

solescout

https://solescout.ai

Registry code: 232e581db6c22d3a

api record

Live sneaker & streetwear prices and in-stock sizes across 600+ US stores, by style code.

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

endpoint
https://solescout.ai/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 solescout live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is solescout free to use?
Yes — the hub reached it with no key and no payment.
What tools does solescout have?
4 tools: where_to_buy, list_brands, search_sneakers, cheapest_for_size.
Is solescout 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
100%

90 days 100%· all time 100%

latency
753ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • 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

_ what it can do 4 tools
3 open 1 never probed 3 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.

  • list_brands open 1h ago

    Brands in the catalogue with product counts. Ground a brand name before searching.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • search_sneakers open 1h ago

    Search the catalogue by model name, colorway or manufacturer style code (e.g. "samba og", "HQ9438"). Returns products with their live lowest price and how many tracked retailers carry each.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "brand": {
      "type": "string",
      "description": "exact brand name from list_brands"
    },
    "limit": {
      "type": "number",
      "description": "max results, default 8, cap 20"
    },
    "query": {
      "type": "string",
      "description": "model, colorway, or style code"
    }
  }
}
    arguments 20 lines
  • cheapest_for_size open 1h ago

    For one product, the cheapest retailer holding EACH size. The winning store differs size to size, so a product-level "lowest price" is usually the wrong answer for a specific buyer.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "size": {
      "type": "string",
      "description": "optional US size, e.g. \"9.5\""
    },
    "slug": {
      "type": "string",
      "description": "product slug"
    }
  }
}
    arguments 16 lines
  • where_to_buy unknown never probed

    Every tracked retailer currently carrying a product, with each one's price, in-stock sizes and a direct link to its own product page. This is the long-tail coverage a feed-based catalogue does not have.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "product slug from search_sneakers"
    }
  }
}
    arguments 12 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 232e581db6c22d3a.

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