# PinPinterest — Pinterest Keyword Research (remote · api.pinpinterest.com)

Pinterest keyword research from our own crawl: saves, competition, related terms, trends, top pins.

- Trust score: 36/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `api.pinpinterest.com`: 36/100 (this document), [markdown](https://verifymcp.io/servers/com-pinpinterest-keywords/api.md), [page](https://verifymcp.io/servers/com-pinpinterest-keywords/api)

## Channel facts

- Endpoint: `https://api.pinpinterest.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.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-11-04.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata.
  - 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.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the PinPinterest — Pinterest Keyword Research MCP server?

PinPinterest — Pinterest Keyword Research is a hosted endpoint at https://api.pinpinterest.com/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.

### Claude

```bash
claude mcp add --transport http com-pinpinterest-keywords 'https://api.pinpinterest.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-pinpinterest-keywords": {
      "url": "https://api.pinpinterest.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-pinpinterest-keywords": {
      "type": "http",
      "url": "https://api.pinpinterest.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-pinpinterest-keywords]
url = "https://api.pinpinterest.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-pinpinterest-keywords --url 'https://api.pinpinterest.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-pinpinterest-keywords:
    url: "https://api.pinpinterest.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-pinpinterest-keywords": {
      "Transport": "http",
      "Url": "https://api.pinpinterest.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-pinpinterest-keywords -t streamable-http -u 'https://api.pinpinterest.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-pinpinterest-keywords": {
      "type": "http",
      "url": "https://api.pinpinterest.com/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-10-25 (score 36, −32)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [security improvement] Authorization: partial → pass
- [security] First check of Authorization: partial
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-24 (score 68)

First indexed and scored.

## MCP tools (8)

### `keyword_lookup` (~199 tokens)

Look up a Pinterest keyword

Pinterest data for one keyword: how many ranking pins we analysed, their average and total saves, competition (low/medium/high) and an opportunity score, plus its niche. est_clicks is an ESTIMATE derived from saves (Pinterest does not publish clicks or impressions for pins you do not own); pins_analysed, saves and competition are measured from the pins we crawled. A keyword we do not hold returns tracked:false with close suggestions and does not use a lookup. Its crawl field says what happens next: on a paid plan we have already started crawling it (crawl.status queued or crawling) — tell the person to ask again in crawl.retry_after_minutes, or that we e-mail them when it is in. When several keywords come back tracked:false, offer request_keywords to queue them all in one call.

Input parameters:

- `term` (string, required): The keyword to look up. A term we do not hold answers tracked:false and costs no lookup.

### `request_keywords` (~173 tokens)

Crawl keywords PinPinterest does not have yet

Ask PinPinterest to crawl Pinterest for keywords it has no data for yet — offer this after keyword_lookup answers tracked:false, especially for a list. Pass up to 25 terms; each comes back with a request_id and a status (queued, crawling, ready, failed). Crawls usually land within 10–40 minutes and the person gets ONE e-mail when they are in; asking keyword_lookup again after crawl.retry_after_minutes returns the data. Asking twice for the same term is the same request. Uses no lookup; up to 25 new keywords a day per account. Needs the Starter plan or above.

Input parameters:

- `terms` (array, required): Up to 25 keywords to crawl. Ones we already hold come back ready; each new one spends one of the 25 a day your account may start. Uses no lookup.

### `related_keywords` (~79 tokens)

Related Pinterest keywords

Keywords that appear on the same ranking pins as yours, strongest overlap first — the ones worth targeting next. Each comes with how many pins it shares and its own competition. Needs the Starter plan or above.

Input parameters:

- `limit` (integer): How many neighbours to return, 1-50.
- `term` (string, required): The keyword to find neighbours for.

### `keyword_top_pins` (~123 tokens)

Top pins for a keyword

The best-performing pins ranking for a keyword, by saves, with their titles, links and save counts — what is winning that search right now. est_clicks is an ESTIMATE derived from saves (Pinterest does not publish clicks or impressions for pins you do not own); pins_analysed, saves and competition are measured from the pins we crawled. Needs the Pro plan or above.

Input parameters:

- `limit` (integer): How many pins to return, 1-50, best first.
- `term` (string, required): The keyword whose ranking pins you want.

### `niche_top_pins` (~316 tokens)

Top pins in a niche

The best-performing pins across a whole niche (use list_niches for the slugs), sorted and paged. Pass next_cursor back as cursor for the next page. There is no impressions sort: Pinterest does not publish impressions for pins you do not own, so we do not invent them. Needs the Pro plan or above.

Input parameters:

- `cursor` (string): The next_cursor from the previous page. Paging is by POSITION, not page number, so a pin whose saves changed between two requests cannot repeat or vanish. Treat it as opaque.
- `limit` (integer): How many pins per page, 1-50. Use `cursor` for the next page.
- `max_age_days` (integer): Only pins Pinterest says were created within this many days. Pins with no known creation date are excluded when this is set.
- `min_saves` (integer): Only pins at or above this many saves.
- `niche` (string, required): ONE slug from /v1/niches. Selecting a parent category includes every subniche beneath it.
- `sort` (string): saves, clicks, engagement, velocity, reactions, recent. There is deliberately NO impressions option: Pinterest does not publish impressions for a pin you do not own, so we will not invent one. Each p…
- `video` (integer): 1 for video pins only, 0 for images only. Omit for both.

### `trending` (~92 tokens)

Rising topics in a niche

Topics rising in a niche right now, read from the pins people are publishing this month, with example pins. Use list_niches for the slugs.

Input parameters:

- `days` (integer): The window the rising reading is measured over.
- `limit` (integer): How many topics to return.
- `niche` (string, required): One to five comma-separated slugs from /v1/niches. `niches` also works.

### `list_niches` (~32 tokens)

List niches

The niche slugs the other tools accept (niche_top_pins, trending). Free — uses no lookup.

### `my_quota` (~34 tokens)

My plan and lookups left

Your PinPinterest plan, how many lookups you have used this month and when they reset. Free — uses no lookup.

## Diagnostics

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

## Score history

- 2026-11-04: 36
- 2026-11-03: 36
- 2026-11-02: 36
- 2026-11-01: 36
- 2026-10-31: 36
- 2026-10-30: 36
- 2026-10-29: 36
- 2026-10-28: 36
- 2026-10-27: 36
- 2026-10-26: 36
- 2026-10-25: 36
- 2026-10-24: 68

## Common questions

### What is the PinPinterest — Pinterest Keyword Research MCP server?

PinPinterest — Pinterest Keyword Research is an MCP server listed in the public MCP registry as com.pinpinterest/keywords. Pinterest keyword research from our own crawl: saves, competition, related terms, trends, top pins. This page covers its hosted endpoint (https://api.pinpinterest.com/mcp).

### Is the PinPinterest — Pinterest Keyword Research MCP server safe to use?

PinPinterest — Pinterest Keyword Research scores 36 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 PinPinterest — Pinterest Keyword Research MCP server expose?

PinPinterest — Pinterest Keyword Research exposes 8 tools: keyword_lookup, request_keywords, related_keywords, keyword_top_pins, niche_top_pins, and 3 more. Their descriptions and schemas cost roughly 1,048 tokens of context every time the server is loaded.

### Does the PinPinterest — Pinterest Keyword Research MCP server require authentication?

Yes. PinPinterest — Pinterest Keyword Research asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the PinPinterest — Pinterest Keyword Research MCP server still maintained?

PinPinterest — Pinterest Keyword Research is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.pinpinterest.com/mcp
- Authorisation metadata: https://api.pinpinterest.com/.well-known/oauth-protected-resource/mcp
- Website: https://pinpinterest.com/developers/mcp?utm_source=mcp-registry
- Changelog RSS feed: https://verifymcp.io/servers/com-pinpinterest-keywords/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-pinpinterest-keywords/api.json
- HTML version of this page: https://verifymcp.io/servers/com-pinpinterest-keywords/api