Inside Ads
REMOTE · APP.INSIDE.AD
Telegram ad exchange: estimate reach and cost with no account, then create and run campaigns.
Available components
Last scanned (3 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 435 tokens (~145/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 20 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 21 Aug 26 0
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- 18 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://app.inside.ad/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.insideads.net | CN=YE1,O=Let's Encrypt,C=US | 19 Oct 2026 | 17 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 57859173167d14a44831781764de5dd7d3b |
| SANs: app-eu.inside.ad, app-fast.insideads.net, app.inside.ad, app.insideads.net | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.inside.ad. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ad. | present | 6062 | 8 | Verified |
| inside.ad. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.inside.ad/api/mcp | Verified | 200 | |
| http (plaintext) | http://app.inside.ad/api/mcp | HTTPS enforced | 301 | https://app.inside.ad/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_campaign_draft ~183
Build a ready-to-launch ad campaign for a product WITHOUT the user having an account yet. Parses the landing page, generates ad creatives, and returns a single checkout link. Give that link to the user: they sign in there, the campaign moves to their account, they pay, and it starts. Use this after estimate_campaign, once the user agreed to advertise. Do NOT ask them to register first.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number | – | Intended budget in USD, used for the estimate shown to the user |
| description | string | – | What the product does, in your own words — improves topic matching |
| geo | string | – | Optional ISO-2 country target, e.g. "US" |
| lang | string | – | Optional audience language, e.g. "en" |
| url | string | yes | Landing page URL of the product to promote (required) |
| Name | Type | Req | Description |
|---|---|---|---|
| adsCreated | number | – | How many ad variants were generated. |
| campaignId | number | – | – |
| checkoutUrl | string | yes | THE link to give the user. One click: sign in, review creatives, pay. |
| draftId | string | yes | Poll get_draft_status with this to see whether the user paid. |
| estimate | object | – | Same shape as estimate_campaign, for the budget given. |
| expiresAt | string | yes | ISO timestamp after which the link stops working. |
No examples provided.
estimate_campaign ~188
Estimate reach, clicks and cost of advertising a product to Telegram audiences — no account or authorization required. Call this FIRST, before asking the user to connect an account: it tells you whether inside.ad has relevant inventory for this product and what a given budget would buy. Describe the product yourself (you know it better than any crawler); the URL alone is a weak signal.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number | – | Budget in USD to estimate against (default 100) |
| description | string | – | What the product does, in your own words. Strongest signal for topic matching. |
| geo | string | – | Optional ISO-2 country filter, e.g. "US" |
| keywords | array | – | Optional topic keywords, e.g. ["devtool","ai"] |
| lang | string | – | Optional audience language filter, e.g. "en" |
| url | string | – | Product landing page URL |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | object | – | – |
| budget | number | yes | Budget the estimate was computed for, in USD |
| cpcRange | object | – | Implied cost per click in USD, derived from CPM and the CTR band. |
| cpmUsd | number | – | Reach-weighted average CPM across matched segments |
| currency | string | yes | – |
| dailyReach | number | – | Total daily impressions available in matched segments |
| deliveryDays | number|null | – | Roughly how many days it takes to deliver estimatedImpressions at the current daily reach. |
| estimatedClicks | object | yes | Range, not a point estimate. Report both ends to the user. |
| estimatedImpressions | number | yes | – |
| inventoryIsThin | boolean | yes | true = there is no matching inventory at all, OR the budget exceeds what the matched inventory can deliver. Say so plainly instead of promising results, and use spendableBudget as the realistic figur… |
| matchedCategories | array | – | – |
| sampleSegments | array | – | Matched inventory segments. Individual channels are deliberately not disclosed. |
| spendableBudget | number | – | How much of the budget this inventory can actually absorb within 30 days. If it is lower than budget, tell the user to either lower the budget or widen targeting — do not promise the full budget will… |
No examples provided.
get_draft_status ~64
Check what happened to a campaign draft you created with create_campaign_draft: whether the user opened the link, signed in and paid. Poll this instead of asking the user to report back.
| Name | Type | Req | Description |
|---|---|---|---|
| draftId | string | yes | draftId returned by create_campaign_draft |
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | number|null | – | – |
| claimedAt | string|null | – | – |
| createdAt | string | – | – |
| draftId | string | yes | – |
| expiresAt | string | – | – |
| hint | string | – | What to tell the user next. |
| previewedAt | string|null | – | – |
| status | string | yes | 'created' — link not opened yet; 'previewed' — user opened it but has not finished; 'claimed' — campaign is on the user's account; 'expired' — link is dead, build a new draft. |
No examples provided.
How do I install the Inside Ads MCP server?
Inside Ads is a hosted endpoint at https://app.inside.ad/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · app.inside.ad
claude mcp add --transport http ad-inside-inside-ads 'https://app.inside.ad/api/mcp'
What is the Inside Ads MCP server?
Inside Ads is an MCP server listed in the public MCP registry as ad.inside/inside-ads. Telegram ad exchange: estimate reach and cost with no account, then create and run campaigns. This page covers its hosted endpoint (https://app.inside.ad/api/mcp).
Is the Inside Ads MCP server safe to use?
Inside Ads scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Inside Ads MCP server expose?
Inside Ads exposes 3 tools: estimate_campaign, create_campaign_draft, get_draft_status. Their descriptions and schemas cost roughly 435 tokens of context every time the server is loaded.
Does the Inside Ads MCP server require authentication?
No. We connected to Inside Ads without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Inside Ads MCP server still maintained?
Inside Ads is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.