com.365pinterest/365-pinterest
365 Pinterest
Is the 365 Pinterest MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-13.
Pinterest automation: schedule pins, manage boards, write AI blogs and auto-pin them.
needs auth probed 2026-11-15 · unchanged since 2026-11-13 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","id":0,"error":{"code":-32001,"message":"Missing credentials — send Authorization: Bearer pk_- Endpoint
- https://365pinterest.com/mcp (streamable-http)
- Host
- 365pinterest.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://365pinterest.com/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server 365pinterest.com, PKCE S256, grants authorization_code, refresh_token.
Scopes openid profile email offline_access pins:read pins:write boards:read wordpress:read wordpress:write.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://365pinterest.com/
- Registry
- active, updated 2026-11-12 · registry entry
Compare this server with others.
More servers
Servers that mention pinterest.
- app.pinsuite/pinsuite · needs auth
- AdaptlyPost com.adaptlypost/mcp-server · needs auth
- WoopSocial Social Media MCP com.woopsocial/mcp · needs auth
- Ads MCP Server by AdKit io.github.adkit/ads · needs auth
- Pinterest Ads MCP Server io.github.cesteral/pinterest-mcp · needs your URL
- Storylayer Publishing io.github.mikeslone/storylayer · needs auth
- io.pinbridge/pinbridge · needs auth
- AIsa Pinterest one.aisa/pinterest · not found
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.