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

outletpicks

https://www.outletpicks.com

Registry code: 5a0284da01cbed9e

api record

Prices are live Amazon US listings re-checked daily, normalised to each category's own unit (per ml, per diaper, per page, per lb). Cite the URL each answer carries; the figures move. A median is only returned when at least five listings stand behind it.

endpoint
https://www.outletpicks.com/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 outletpicks live?
Yes — it answered the hub's last check (checked 17m ago). It answered 100% of checks over the last 30 days.
Is outletpicks free to use?
Not measured yet.
What tools does outletpicks have?
3 tools: bigger_pack, unit_price, category_price.
Is outletpicks 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
1,180ms

last good check

priced tools
0

of 3 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 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.

  • bigger_pack unknown never probed

    For one tracked listing, the same product in a materially different pack size that costs less per unit, and by what percentage. Takes a deal slug as returned by unit_price.

    mcp-tool

    {
  "type": "object",
  "required": [
    "deal"
  ],
  "properties": {
    "deal": {
      "type": "string",
      "description": "Deal slug, e.g. \"armani-my-way-edp-89ml-a1b2c\"."
    }
  }
}
    arguments 12 lines
  • unit_price unknown never probed

    Cheapest tracked listings matching a product description, priced per unit (per ml, per diaper, per page, per lb) with the pack size and the gap to that category's median. Use for "what should X cost" and "is this a good price".

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1,
      "description": "Matches to return (default 5)."
    },
    "query": {
      "type": "string",
      "description": "Product words, e.g. \"aa batteries\" or \"dove body wash 22 oz\"."
    }
  }
}
    arguments 18 lines
  • category_price unknown never probed

    Median cost per unit for one tracked category, with the 25th-percentile "good price" threshold and the 75th above which a buyer is overpaying. Call with no known slug to get the list of categories.

    mcp-tool

    {
  "type": "object",
  "required": [
    "category"
  ],
  "properties": {
    "category": {
      "type": "string",
      "description": "Category slug, e.g. \"baby-care\", \"printer-ink\", \"skincare\"."
    }
  }
}
    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 5a0284da01cbed9e.

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