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

who-ai-picks

https://agnostify.com

Registry code: 84d977f00f58d6b3

api record

Who AI Sends Buyers MCP. Read-only access to the published boards at https://agnostify.com/ai-picks. A score is the share of valid logged-out United States runs that name a brand, over a rolling four weeks, ordered by the low end of the 95% Wilson interval. This server does not start a collection run and does not call a model. When percent is null, the website shows a dash. Do not treat that as zero. When status is pending or offline, no score was published. Do not fill one in.

endpoint
https://agnostify.com/ai-picks/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 who-ai-picks live?
Yes — it answered the hub's last check (checked 16h ago). It answered 100% of checks over the last 30 days.
Is who-ai-picks free to use?
Yes — the hub reached it with no key and no payment.
What tools does who-ai-picks have?
7 tools: get_category_board, get_question, get_brand, get_movers, list_categories, list_questions, describe_method.
Is who-ai-picks 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
314ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 2 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 7 tools
3 open 4 never probed 3 of 7 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_categories open 16h ago

    List the Who AI Sends Buyers category boards and their public URLs. No scores.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • list_questions open 16h ago

    List the fixed buyer questions on a board, or every question. No scores.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "category": {
      "enum": [
        "geo",
        "crm",
        "meetings",
        "email",
        "social",
        "ugc"
      ],
      "type": "string",
      "description": "Board id. Omit for every question."
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • describe_method open 16h ago

    The published measurement method. No scores.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_category_board unknown never probed

    The published category board: brands ordered as on the website, with the same counts. Empty when nothing has been published.

    mcp-tool

    {
  "type": "object",
  "required": [
    "category"
  ],
  "properties": {
    "category": {
      "enum": [
        "geo",
        "crm",
        "meetings",
        "email",
        "social",
        "ugc"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
  • get_question unknown never probed

    How often each brand is named on one published question. The slug is the question page slug.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "pattern": "^[a-z0-9-]+$",
      "maxLength": 80,
      "minLength": 1
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • get_brand unknown never probed

    One reviewed brand's row on each board it is scored on. Unknown names are not given a score.

    mcp-tool

    {
  "type": "object",
  "required": [
    "brand"
  ],
  "properties": {
    "brand": {
      "type": "string",
      "pattern": "^[a-z0-9-]+$",
      "maxLength": 80,
      "minLength": 1
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • get_movers unknown never probed

    Week-over-week brand movers using the same rule as the movers page. A short history returns no movers.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1,
      "description": "Risers and fallers each, per board. Default 3, the page cap."
    },
    "category": {
      "enum": [
        "geo",
        "crm",
        "meetings",
        "email",
        "social",
        "ugc"
      ],
      "type": "string",
      "description": "Board id. Omit for every board."
    }
  },
  "additionalProperties": false
}
    arguments 24 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 84d977f00f58d6b3.

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