Pickrate
REMOTE · PICKRATE.IO
Agent analytics: which AI agents read your site, drove signups, and pick you over competitors.
Available components
Last scanned (16 hours ago)
Scores higher than 95% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 497 tokens (~124/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Aug 26 0
- Authorization: unverified → partial ▲ security
- DNSSEC: fail → pass ▲ security
- Tool “getPickRate” rewrote its description, which is the text the model reads security
- Schema quality: excellent → good functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Probed https://pickrate.io/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pickrate.io | CN=YR1,O=Let's Encrypt,C=US | 24 Oct 2026 | 22 Jan 2027 | RSA 2048 | SHA256-RSA | 58b79e35f785d476561b5392cc403803889 |
| SANs: pickrate.io | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of pickrate.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| pickrate.io. | DS published | 2371 | 13 | Verified |
| pickrate.io. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pickrate.io/api/mcp | Verified | 200 | |
| http (plaintext) | http://pickrate.io/api/mcp | HTTPS enforced | 301 | https://pickrate.io/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
getLeaderboard ~76
Get the ranked list of tools for a category by Pick Rate. Omit category to list available categories (optionally scoped by domain).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category slug (e.g. 'payments', 'auth', 'search'). Optional. |
| domain | string | – | When listing categories, scope to one leaderboard tree. Optional. |
No output schema declared.
No examples provided.
getMyAgents ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| windowDays | number | – | Days to look back (default 30, max 90). |
No output schema declared.
No examples provided.
getPickRate ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| tool | string | yes | Tool name, slug, domain, or package (e.g. 'stripe', 'clerk', '@sendgrid/mail'). |
No output schema declared.
No examples provided.
lookupTool ~52
Resolve a tool name, slug, domain, or package to its Pickrate report (Pick Rate, rank, who beats it).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search term: name, slug, domain, or package. |
No output schema declared.
No examples provided.
How do I install the Pickrate MCP server?
Pickrate is a hosted endpoint at https://pickrate.io/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · pickrate.io
claude mcp add --transport http io-pickrate-pickrate 'https://pickrate.io/api/mcp'
What is the Pickrate MCP server?
Pickrate is an MCP server listed in the public MCP registry as io.pickrate/pickrate. Agent analytics: which AI agents read your site, drove signups, and pick you over competitors. This page covers its hosted endpoint (https://pickrate.io/api/mcp).
Is the Pickrate MCP server safe to use?
Pickrate scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Pickrate MCP server expose?
Pickrate exposes 4 tools: getPickRate, getLeaderboard, lookupTool, getMyAgents. Their descriptions and schemas cost roughly 371 tokens of context every time the server is loaded.
Does the Pickrate MCP server require authentication?
No. We connected to Pickrate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Pickrate MCP server still maintained?
Pickrate is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Pickrate MCP server?
VerifyMCP ran 13 checks on Pickrate, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.