Telegram ad exchange: estimate reach and cost with no account, then create and run campaigns.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://app.inside.ad/api/mcp3 tools · 946msestimate_campaignEstimate 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 th…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 th…
| Parameter | Type | Description |
|---|---|---|
| url | string | Product landing page URL |
| description | string | What the product does, in your own words. Strongest signal for topic matching. |
| keywords | array | Optional topic keywords, e.g. ["devtool","ai"] |
| budget | number | Budget in USD to estimate against (default 100) |
| geo | string | Optional ISO-2 country filter, e.g. "US" |
| lang | string | Optional audience language filter, e.g. "en" |
create_campaign_draftBuild 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…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…
| Parameter | Type | Description |
|---|---|---|
| url* | string | Landing page URL of the product to promote (required) |
| description | string | What the product does, in your own words — improves topic matching |
| budget | number | Intended budget in USD, used for the estimate shown to the user |
| geo | string | Optional ISO-2 country target, e.g. "US" |
| lang | string | Optional audience language, e.g. "en" |
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. Poll this instead of asking the user to report back.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.
| Parameter | Type | Description |
|---|---|---|
| draftId* | string | draftId returned by create_campaign_draft |
3 of 3 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Telegram ad exchange: estimate reach and cost with no account, then create and run campaigns.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.