Skip to content

Inside Ads MCP server

ad.inside/inside-adsinside.adstreamable-httpv1.0.0Scanned

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

3 tools: 2 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 2
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Inside Ads MCP server can do

The Inside Ads MCP server is published by inside.ad, a domain the MCP Registry verified. It has 3 tools. It can create or change data (2 tools: estimate_campaign and create_campaign_draft), but cannot delete data. 1 tool only reads.

2 tools can send data out of your system (estimate_campaign and create_campaign_draft).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 11, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 2Claude Code: ask
  • create_campaign_draftBuild a ready-to-launch ad campaign for a product WITHOUT the user having an account yet.Can send data outNo findings

    Why it is in this group

    • The name "create_campaign_draft" says "create": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.
  • estimate_campaignEstimate reach, clicks and cost of advertising a product to Telegram audiences — no account or authorization required.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.
Only reads 1Show 1 read-only tool
  • get_draft_statusCheck what happened to a campaign draft you created with create_campaign_draft: whether the user opened the link, signed in and paid.No findings

    Why it is in this group

    • The name "get_draft_status" says "get": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:24 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://app.inside.ad/.well-known/oauth-protected-resource/api/mcp
Authorization servers
https://app.inside.ad
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://app.inside.ad/api/mcp: tools/list returned 3 tools to an anonymous client, including estimate_campaign (write), create_campaign_draft (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__inside-ads__get_draft_status"
    ],
    "ask": [
      "mcp__inside-ads__estimate_campaign",
      "mcp__inside-ads__create_campaign_draft"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as inside-ads. Review it before you use it.

Capability tags behind 2 rules
  • mcp__inside-ads__estimate_campaign outbound
  • mcp__inside-ads__create_campaign_draft outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ad.inside/inside-ads/verify?hash=c81c5621e12fc3ac70f256fb00cfa6ca5fdc7e2ab062f667fe8453b85bd4099d" | jq -e '.changed == false'

Pinned hash c81c5621e12f, from Nov 11, 2026, 16:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ad.inside/inside-ads/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ad.inside/inside-ads
[![Anlyon Radar](https://radar.anlyon.com/badge/ad.inside/inside-ads.svg)](https://radar.anlyon.com/servers/ad.inside/inside-ads)

Source: MCP Registry. Synced Oct 21, 2026, 17:41 UTC.

Inside Ads MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Inside Ads MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Inside Ads MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Inside Ads MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Inside Ads MCP server have?

3 tools: 2 write, 1 read. estimate_campaign, create_campaign_draft and get_draft_status.

Does the Inside Ads MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Inside Ads MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): estimate_campaign and create_campaign_draft.

Has the Inside Ads MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.