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

Pickrate

https://pickrate.io

Registry code: 1714e311d559a1d9

api record

Pickrate measures whether AI agents pick a developer tool over its competitors on unbranded tasks. Use getPickRate for one tool's headline number, getLeaderboard for a category ranking (omit the category to list categories), and lookupTool to resolve a name/slug/domain/package to its report. If the caller connected their own Pickrate account (an API key in the Authorization header), use getMyAgents to answer questions about the AI agents driving THEIR business — how much traffic agents drive, how many signups/conversions they've sent, and how much revenue — so they can just ask instead of…

endpoint
https://pickrate.io/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
1,028ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 4 tools
1 open1 auth-required 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.

  • getLeaderboard open 1h ago

    Get the ranked list of tools for a category by Pick Rate. Omit category to list available categories (optionally scoped by domain).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "domain": {
      "enum": [
        "dev-tools",
        "saas"
      ],
      "type": "string",
      "description": "When listing categories, scope to one leaderboard tree. Optional."
    },
    "category": {
      "type": "string",
      "description": "Category slug (e.g. 'payments', 'auth', 'search'). Optional."
    }
  }
}
    arguments 17 lines
  • getMyAgents auth-required 1h ago

    Get YOUR own Pickrate agent analytics — answer questions like 'how much traffic are agents driving?', 'how many signups/conversions have agents sent me?', and 'how much revenue have they influenced?'. Returns the outcome (agent-driven conversions by kind, revenue, top converting agents) and the source (which agents read your site, your most-read pages, gaps, and the trend). Lets the user just ask instead of opening a dashboard. Requires the user's Pickrate API key as a Bearer token in the Authorization header.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "windowDays": {
      "type": "number",
      "description": "Days to look back (default 30, max 90)."
    }
  }
}
    arguments 9 lines
  • getPickRate unknown never probed

    Get the headline Pick Rate and rank for a single developer tool — the share of the time AI agents pick it over competitors on unbranded tasks. Also returns that vendor's agent readiness level (what it publishes for agents), which is a separate signal: across this corpus readiness barely predicts Pick Rate, so don't infer one from the other.

    mcp-tool

    {
  "type": "object",
  "required": [
    "tool"
  ],
  "properties": {
    "tool": {
      "type": "string",
      "description": "Tool name, slug, domain, or package (e.g. 'stripe', 'clerk', '@sendgrid/mail')."
    }
  }
}
    arguments 12 lines
  • lookupTool unknown never probed

    Resolve a tool name, slug, domain, or package to its Pickrate report (Pick Rate, rank, who beats it).

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Search term: name, slug, domain, or package."
    }
  }
}
    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.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/1714e311d559a1d9/badge.svg)](https://brick.blue/agent/1714e311d559a1d9)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ 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.