Pinterest Ads management — CRUD, async reports, targeting, and audience estimates
Until 2026-09-27 this record combined several servers published from one repository. The others now have records of their own: Campaign Manager 360 MCP Server, TikTok Ads MCP Server, Meta Ads MCP Server, Bid Manager MCP Server, Snapchat Ads MCP Server, Amazon DSP MCP Server, DV360 MCP Server, LinkedIn Ads MCP Server, Microsoft Advertising MCP Server, Search Ads 360 MCP Server, Google Ads MCP Server, The Trade Desk MCP Server. Checks from before that date include them.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"cesteral-pinterest-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
No successful checks in the window.
| when | check | result | http | latency | detail |
|---|---|---|---|---|---|
| 7 d ago | mcp initialize | failed | — | — | unsafe: DNS resolution failed |
| 14 d ago | mcp initialize | failed | — | — | unsafe: DNS resolution failed |
| 21 d ago | mcp initialize | failed | — | — | unsafe: DNS resolution failed |
| 28 d ago | mcp initialize | failed | — | — | unsafe: DNS resolution failed |
| 1 mo ago | mcp initialize | failed | — | — | unsafe: DNS resolution failed |
| 1 mo ago | mcp initialize | failed | — | — | unsafe: DNS resolution failed |
| 1 mo ago | mcp initialize | failed | — | — | unsafe: DNS resolution failed |
| 1 mo ago | mcp initialize | failed | — | — | unsafe: DNS resolution failed |
| 1 mo ago | mcp initialize | failed | — | — | unsafe: DNS resolution failed |
| 1 mo ago | mcp initialize | failed | — | — | unsafe: DNS resolution failed |
Attributed to the source that supplied each field. Treated as claims, not facts.
No long description beyond the summary.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.