# Inside Ads (remote · app.inside.ad)

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

- Trust score: 80/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `app.inside.ad`: 80/100 (this document), [markdown](https://verifymcp.io/servers/ad-inside-inside-ads/api-mcp.md), [page](https://verifymcp.io/servers/ad-inside-inside-ads/api-mcp)

## Channel facts

- Endpoint: `https://app.inside.ad/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http ad-inside-inside-ads 'https://app.inside.ad/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ad-inside-inside-ads": {
      "url": "https://app.inside.ad/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ad-inside-inside-ads": {
      "type": "http",
      "url": "https://app.inside.ad/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ad-inside-inside-ads]
url = "https://app.inside.ad/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ad-inside-inside-ads": {
      "type": "remote",
      "url": "https://app.inside.ad/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ad-inside-inside-ads --url 'https://app.inside.ad/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ad-inside-inside-ads:
    url: "https://app.inside.ad/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ad-inside-inside-ads": {
      "Transport": "http",
      "Url": "https://app.inside.ad/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ad-inside-inside-ads -t streamable-http -u 'https://app.inside.ad/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ad-inside-inside-ads": {
      "type": "http",
      "url": "https://app.inside.ad/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 80, +1)

- [security] Stability: 0.97 → pass

### 2026-09-18 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `estimate_campaign` (~188 tokens)

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.

Input parameters:

- `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

Output parameters:

- `assumptions` (object)
- `budget` (number): 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)
- `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): Range, not a point estimate. Report both ends to the user.
- `estimatedImpressions` (number)
- `inventoryIsThin` (boolean): 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…

### `create_campaign_draft` (~183 tokens)

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.

Input parameters:

- `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, required): Landing page URL of the product to promote (required)

Output parameters:

- `adsCreated` (number): How many ad variants were generated.
- `campaignId` (number)
- `checkoutUrl` (string): THE link to give the user. One click: sign in, review creatives, pay.
- `draftId` (string): 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): ISO timestamp after which the link stops working.

### `get_draft_status` (~64 tokens)

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.

Input parameters:

- `draftId` (string, required): draftId returned by create_campaign_draft

Output parameters:

- `campaignId` (number|null)
- `claimedAt` (string|null)
- `createdAt` (string)
- `draftId` (string)
- `expiresAt` (string)
- `hint` (string): What to tell the user next.
- `previewedAt` (string|null)
- `status` (string): '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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ad-inside-inside-ads/api-mcp#diagnostics

## Score history

- 2026-09-20: 80
- 2026-09-19: 79
- 2026-09-18: 79
- 2026-09-17: 78
- 2026-09-16: 78
- 2026-09-15: 77
- 2026-09-14: 77
- 2026-09-13: 76
- 2026-09-12: 76
- 2026-09-11: 75
- 2026-09-10: 75
- 2026-09-09: 74
- 2026-09-08: 74
- 2026-09-07: 74
- 2026-09-06: 73
- 2026-09-05: 73
- 2026-09-04: 72
- 2026-09-03: 72
- 2026-09-02: 71
- 2026-09-01: 71
- 2026-08-31: 70
- 2026-08-30: 70
- 2026-08-29: 69
- 2026-08-28: 69
- 2026-08-27: 68
- 2026-08-26: 68
- 2026-08-25: 66
- 2026-08-24: 65
- 2026-08-23: 65
- 2026-08-22: 64

## Common questions

### 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://app.inside.ad/api/mcp
- Website: https://inside.ad/
- Changelog RSS feed: https://verifymcp.io/servers/ad-inside-inside-ads/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ad-inside-inside-ads/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ad-inside-inside-ads/api-mcp