mcp server
Pickrate
Agent analytics: which AI agents read your site, drove signups, and pick you over competitors.
Description as published by the maintainer. Source
- version 1.1.0
- active
- analytics
active — Registry entry last updated 2026-08-01. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
getLeaderboard(domain, category)- Get the ranked list of tools for a category by Pick Rate. Omit category to list available categories (optionally scoped by domain).
getMyAgents(windowDays)- 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.
getPickRate(tool)- 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. Required: tool.
lookupTool(query)- Resolve a tool name, slug, domain, or package to its Pickrate report (Pick Rate, rank, who beats it). Required: query.
Last successful function declaration observed on . Source: https://pickrate.io/api/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://pickrate.io/api/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-01 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-08-01 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 4 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | pickrate.io | |
| mcp endpoint status | ok | The server listed 4 functions when asked. | as of probe | pickrate.io |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json