Pickrate
Agent analytics: which AI agents read your site, drove signups, and pick you over competitors.
Should I use this
Quality & Safety
Findings (1)
- LOWin lookupTool
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"pickrate": {
"url": "https://pickrate.io/api/mcp"
}
}
}Remote endpoints
https://pickrate.io/api/mcpstreamable-httpWhat it can do
Tool inventory
Tools (4)
🟢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.
Input Schema
{
"type": "object",
"properties": {
"tool": {
"type": "string",
"description": "Tool name, slug, domain, or package (e.g. 'stripe', 'clerk', '@sendgrid/mail')."
}
},
"required": [
"tool"
]
}🟢getLeaderboard(category, domain)
Get the ranked list of tools for a category by Pick Rate. Omit category to list available categories (optionally scoped by domain).
Input Schema
{
"type": "object",
"properties": {
"category": {
"type": "string",
"description": "Category slug (e.g. 'payments', 'auth', 'search'). Optional."
},
"domain": {
"type": "string",
"enum": [
"dev-tools",
"saas"
],
"description": "When listing categories, scope to one leaderboard tree. Optional."
}
}
}🟢lookupTool(query)
Resolve a tool name, slug, domain, or package to its Pickrate report (Pick Rate, rank, who beats it).
Input Schema
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "Search term: name, slug, domain, or package."
}
},
"required": [
"query"
]
}🟢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.
Input Schema
{
"type": "object",
"properties": {
"windowDays": {
"type": "number",
"description": "Days to look back (default 30, max 90)."
}
}
}Recommended Prompts
getPickRategetPickRateCommunity
Evidence