PinPinterest — Pinterest Keyword Research
REMOTE · API.PINPINTEREST.COM
Pinterest keyword research from our own crawl: saves, competition, related terms, trends, top pins.
Available components
Last scanned (20 hours ago)
Scores higher than 19% of remote servers
Reachable. Last reached 4 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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
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. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 25 Oct 26 −32
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: partial → pass ▲ security
- First check of Authorization: partial security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 24 Oct 26 68
First indexed and scored.
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 4 Nov 2026 · Probed https://api.pinpinterest.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.pinpinterest.com | CN=YE1,O=Let's Encrypt,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5a5cf19ec6f8e1b0025486bd343829bfb9b |
| SANs: api.pinpinterest.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.pinpinterest.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| pinpinterest.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="PinPinterest", resource_metadata="https://api.pinpinterest.com/.well-known/oauth-protected-resource/mcp"
Bearer realm="PinPinterest", resource_metadata="https://api.pinpinterest.com/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| www-authenticate | Bearer realm="PinPinterest", resource_metadata="https://api.pinpinterest.com/.well-known/oauth-protected-resource/mcp" |
Protected resource metadata
| Document | https://api.pinpinterest.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://api.pinpinterest.com/mcp |
| Authorisation server | https://api.pinpinterest.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.pinpinterest.com/mcp | Auth required | 401 | |
| http (plaintext) | http://api.pinpinterest.com/mcp | HTTPS enforced | 301 | https://api.pinpinterest.com/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 →
keyword_lookup Look up a Pinterest keyword ~199
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.
| Name | Type | Req | Description |
|---|---|---|---|
| term | string | yes | The keyword to look up. A term we do not hold answers tracked:false and costs no lookup. |
No output schema declared.
No examples provided.
keyword_top_pins Top pins for a keyword ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many pins to return, 1-50, best first. |
| term | string | yes | The keyword whose ranking pins you want. |
No output schema declared.
No examples provided.
list_niches List niches ~32
The niche slugs the other tools accept (niche_top_pins, trending). Free — uses no lookup.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
my_quota My plan and lookups left ~34
Your PinPinterest plan, how many lookups you have used this month and when they reset. Free — uses no lookup.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
niche_top_pins Top pins in a niche ~316
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
related_keywords Related Pinterest keywords ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many neighbours to return, 1-50. |
| term | string | yes | The keyword to find neighbours for. |
No output schema declared.
No examples provided.
request_keywords Crawl keywords PinPinterest does not have yet ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| terms | array | yes | 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. |
No output schema declared.
No examples provided.
trending Rising topics in a niche ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | The window the rising reading is measured over. |
| limit | integer | – | How many topics to return. |
| niche | string | yes | One to five comma-separated slugs from /v1/niches. `niches` also works. |
No output schema declared.
No examples provided.
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.
remote · api.pinpinterest.com
claude mcp add --transport http com-pinpinterest-keywords 'https://api.pinpinterest.com/mcp'
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.