# Pickrate (remote · pickrate.io)

Agent analytics: which AI agents read your site, drove signups, and pick you over competitors.

- Trust score: 67/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `pickrate.io`: 67/100 (this document), [markdown](https://verifymcp.io/servers/io-pickrate-pickrate/api-mcp.md), [page](https://verifymcp.io/servers/io-pickrate-pickrate/api-mcp)

## Channel facts

- Endpoint: `https://pickrate.io/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 459 tokens (~114/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http io-pickrate-pickrate https://pickrate.io/api/mcp
```

### Codex

```toml
[mcp_servers.io-pickrate-pickrate]
url = "https://pickrate.io/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-pickrate-pickrate": {
      "type": "remote",
      "url": "https://pickrate.io/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-pickrate-pickrate --url https://pickrate.io/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-pickrate-pickrate:
    url: "https://pickrate.io/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "io-pickrate-pickrate": {
      "type": "http",
      "url": "https://pickrate.io/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (4)

### `getPickRate` (~70 tokens)

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.

Input parameters:

- `tool` (string, required): Tool name, slug, domain, or package (e.g. 'stripe', 'clerk', '@sendgrid/mail').

### `getLeaderboard` (~76 tokens)

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

Input parameters:

- `category` (string): Category slug (e.g. 'payments', 'auth', 'search'). Optional.
- `domain` (string): When listing categories, scope to one leaderboard tree. Optional.

### `lookupTool` (~52 tokens)

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

Input parameters:

- `query` (string, required): Search term: name, slug, domain, or package.

### `getMyAgents` (~135 tokens)

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 parameters:

- `windowDays` (number): Days to look back (default 30, max 90).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-pickrate-pickrate/api-mcp#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 67
- 2026-08-01: 66
- 2026-07-31: 66
- 2026-07-30: 66
- 2026-07-29: 66
- 2026-07-28: 65
- 2026-07-27: 64
- 2026-07-26: 64

## Links

- Remote endpoint: https://pickrate.io/api/mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-pickrate-pickrate/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-pickrate-pickrate/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-pickrate-pickrate/api-mcp