Publish and schedule Pinterest pins from any MCP client. Token refresh and retries handled.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Every successful check was an authentication response (401/403). The endpoint exists and enforces authentication; nothing behind that boundary — tools, behaviour, service health — has been observed. Latency here is time to authentication response. Tools: not measured — authentication required.
Not distributed through a package registry we index.
| when | check | result | http | latency | detail |
|---|---|---|---|---|---|
| 31 min ago | mcp initialize | ok | 401 | 106 ms | auth required |
| 1 h ago | mcp initialize | ok | 401 | 126 ms | auth required |
| 2 h ago | mcp initialize | ok | 401 | 132 ms | auth required |
| 3 h ago | mcp initialize | ok | 401 | 119 ms | auth required |
| 4 h ago | mcp initialize | ok | 401 | 154 ms | auth required |
| 5 h ago | mcp initialize | ok | 401 | 154 ms | auth required |
| 6 h ago | mcp initialize | ok | 401 | 141 ms | auth required |
| 7 h ago | mcp initialize | ok | 401 | 206 ms | auth required |
Attributed to the source that supplied each field. Treated as claims, not facts.
PinBridge is a hosted Pinterest publishing API with an MCP server, so an assistant can create pins, manage boards and schedule posts directly. Connect a Pinterest account once and PinBridge handles OAuth token refresh, rate limits, retries and delivery status. 17 tools; the five write tools are off by default. Free tier available.
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.
| 8 h ago |
| mcp initialize |
| ok |
| 401 |
| 223 ms |
| auth required |
| 9 h ago | mcp initialize | ok | 401 | 129 ms | auth required |
Sequenzy MCP server for AI-powered email marketing automation.