com.insightfulpipe/snapchat-ads
Snapchat Ads MCP by InsightfulPipe
Is the Snapchat Ads MCP by InsightfulPipe MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-26.
Hosted Snapchat Ads MCP server, with each action switched on or off per account.
needs auth probed 2026-11-15 · unchanged since 2026-10-26 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error": "invalid_token", "error_description": "Authentication failed. The provided bearer token is invalid, - Endpoint
- https://snapchat-ads.insightfulmcp.com/ (streamable-http)
- Host
- snapchat-ads.insightfulmcp.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://snapchat-ads.insightfulmcp.com/ registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server snapchat-ads.insightfulmcp.com, PKCE S256, grants authorization_code, refresh_token.
Scopes mcp_connection.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/Insightful-Pipe/snapchat-ads-mcp-server
- Website
- https://insightfulpipe.com/mcp-servers/snapchat-ads
- Registry
- active, updated 2026-10-21 · registry entry
Compare this server with others.
More servers
Servers that mention snapchat.
- co.pipeboard/snap-ads-mcp · needs auth
- How To Make Money On Snapchat com.howtomakemoneyonsnapchat/creator-monetization · alive
- Snapchat Ads MCP Server io.github.cesteral/snapchat-mcp · needs your URL
- AdLiftr: Meta (Facebook & Instagram), TikTok, Google Ads & Snapchat com.adliftr/adliftr · needs auth
- AdAce Ads website.adace/ads · needs auth
- uplads com.uplads/uplads · needs auth
- Snapchat Ads com.getmcpads/snapchat-ads · crashed on start
- Apogee: Bulk Ad Launcher for Meta, TikTok & Snapchat ad.apogee/apogee · needs auth
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.