_ registry / mcp streamable-http · checked 13h ago

inside-ads

https://app.inside.ad

Registry code: cb379b06291767a8

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://app.inside.ad/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is inside-ads live?
Yes — it answered the hub's last check (checked 13h ago). It answered 99% of checks over the last 30 days.
Is inside-ads free to use?
Yes — the hub reached it with no key and no payment.
What tools does inside-ads have?
3 tools: estimate_campaign, create_campaign_draft, get_draft_status.
Is inside-ads safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.1%

90 days 99.1%· all time 99.1%

latency
115ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 211 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
productivity & business marketing & seo
used for
  • estimate reach and cost of a telegram ad
  • create an ad campaign draft
  • check campaign draft status
takes → gives
text → data
tools
2 reads1 changes data
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • estimate_campaign reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "geo": {
      "type": "string",
      "description": "Optional ISO-2 country filter, e.g. \"US\""
    },
    "url": {
      "type": "string",
      "description": "Product landing page URL"
    },
    "lang": {
      "type": "string",
      "description": "Optional audience language filter, e.g. \"en\""
    },
    "budget": {
      "type": "number",
      "description": "Budget in USD to estimate against (default 100)"
    },
    "keywords": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional topic keywords, e.g. [\"devtool\",\"ai\"]"
    },
    "description": {
      "type": "string",
      "description": "What the product does, in your own words. Strongest signal for topic matching."
    }
  },
  "additionalProperties": false
}
    arguments 33 lines
  • create_campaign_draft changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "geo": {
      "type": "string",
      "description": "Optional ISO-2 country target, e.g. \"US\""
    },
    "url": {
      "type": "string",
      "description": "Landing page URL of the product to promote (required)"
    },
    "lang": {
      "type": "string",
      "description": "Optional audience language, e.g. \"en\""
    },
    "budget": {
      "type": "number",
      "description": "Intended budget in USD, used for the estimate shown to the user"
    },
    "description": {
      "type": "string",
      "description": "What the product does, in your own words — improves topic matching"
    }
  },
  "additionalProperties": false
}
    arguments 29 lines
  • get_draft_status reads unknown 13h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "draftId"
  ],
  "properties": {
    "draftId": {
      "type": "string",
      "description": "draftId returned by create_campaign_draft"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id cb379b06291767a8.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/cb379b06291767a8/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/cb379b06291767a8/badge.svg)](https://brick.blue/agent/cb379b06291767a8?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.