Inside Ads

warnings

app.inside.ad

Telegram ad exchange: estimate reach and cost with no account, then create and run campaigns.

https://app.inside.ad/api/mcpWebsiteOAuthMCP 2025-06-18v1.0.0last checked 24 Aug 2026spoke MCP on 3 of 3 checks (30 days)initialize in 443 ms

How to authenticate

Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	OAuth
Issuer	https://app.inside.ad
Dynamic client registration	✓Advertised (RFC 7591)
Client ID Metadata Document	✕Not advertised
PKCE	✓S256
Grant types	authorization_code, refresh_token
Scopes	ads:read, ads:write, stats:read, profile:read, profile:write, content:write, channels:read, channels:write
Protected-resource metadata	✓Published (RFC 9728)
Anonymous access	Handshake succeeds; 3 tools listable
Credentials demanded in prose	✕estimate_campaign These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.

What the probe found

warningTools needing credentials are listed without a challenge

1 of the 3 tools listed anonymously say in their own descriptions that they need an account or a key (estimate_campaign), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

3 tools usable without signing in

The server exposes a public surface before authorization: estimate_campaign, create_campaign_draft, get_draft_status.

Tools

create_campaign_draftestimate_campaignget_draft_status

Contract history

24 Aug 2026v1.0.0first recorded contract

Get alerted when this contract changes

Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/inside-ads/badge.svg)](https://mcpi.app/servers/inside-ads)