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

tryselltheclick

https://www.tryselltheclick.com

Registry code: a6e2ed00163ec51f

api record

tryselltheclick provides three read-only Meta ad tools for online stores: keep_or_kill (keep, kill or too early, from profit per sale, spend and sales), find_where_ad_breaks (before the click, after it or on price, against Triple Whale benchmarks) and plan_ad_test (how many new ads to test, for how long, and which setup).

endpoint
https://www.tryselltheclick.com/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 tryselltheclick live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is tryselltheclick free to use?
Yes — the hub reached it with no key and no payment.
What tools does tryselltheclick have?
3 tools: keep_or_kill, plan_ad_test, find_where_ad_breaks.
Is tryselltheclick 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
100%

90 days 100%· all time 100%

latency
259ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

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.

  • keep_or_kill unknown 1h ago

    Should I keep, pause or kill this Meta (Facebook/Instagram) ad? Give what one sale leaves the store before ad costs, what the ad has spent, and how many sales it brought, plus days running and link clicks if known. Returns keep, kill or too early, money up or down so far, the chance it really makes money, and the next step.

    mcp-tool

    {
      "type": "object",
      "required": [
        "profit_per_sale",
        "amount_spent",
        "sales"
      ],
      "properties": {
        "sales": {
          "type": "integer",
          "description": "Sales (purchases) the ad brought."
        },
        "link_clicks": {
          "type": "number",
          "description": "Optional. Link clicks on the ad. With no sales, fewer than 53 clicks is too few to judge unless the clicks themselves cost too much."
        },
        "amount_spent": {
          "type": "number",
          "description": "What the ad has spent so far."
        },
        "days_running": {
          "type": "number",
          "description": "Optional. Days the ad has been running. Under 3 days, a kill is held back unless the loss is already clear."
        },
        "profit_per_sale": {
          "type": "number",
          "description": "What one sale leaves the store before ad costs: price minus product, shipping, fees and returns (break-even CPA)."
        }
      }
    }
    arguments 30 lines
  • plan_ad_test unknown 1h ago

    How many new Meta ads should I test, for how long, and should I use ABO or one ad set? Give the number of new ads, the budget a day and the usual cost per sale.

    mcp-tool

    {
      "type": "object",
      "required": [
        "new_ads",
        "budget_per_day",
        "cost_per_sale"
      ],
      "properties": {
        "new_ads": {
          "type": "integer"
        },
        "cost_per_sale": {
          "type": "number",
          "description": "Usual cost per purchase (CPA)."
        },
        "budget_per_day": {
          "type": "number"
        },
        "cost_per_1000_views": {
          "type": "number",
          "description": "Optional CPM, used when sales are too few to judge on. Default 15."
        }
      }
    }
    arguments 24 lines
  • find_where_ad_breaks unknown 1h ago

    Why isn't my Meta ad selling? Give the last 7 days of impressions, link clicks, purchases and amount spent from Ads Manager. Returns whether it breaks before the click, after the click or on price, compared with Triple Whale benchmarks from 40,000+ ecommerce brands, and what to fix first.

    mcp-tool

    {
      "type": "object",
      "required": [
        "impressions",
        "link_clicks",
        "purchases",
        "amount_spent"
      ],
      "properties": {
        "industry": {
          "type": "string",
          "description": "Optional, e.g. skincare, supplements, apparel, food."
        },
        "purchases": {
          "type": "number"
        },
        "impressions": {
          "type": "number"
        },
        "link_clicks": {
          "type": "number"
        },
        "amount_spent": {
          "type": "number"
        }
      }
    }
    arguments 27 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 a6e2ed00163ec51f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a6e2ed00163ec51f/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/a6e2ed00163ec51f/badge.svg)](https://brick.blue/agent/a6e2ed00163ec51f?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.