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

sponsor-radar

https://bookasponsor.com

Registry code: b3baf2de75af754c

api record

Book a Sponsor knows which brands sponsor newsletters, read from published issues. For a specific newsletter, call find_newsletter_sponsors with its web address; if the scan is still running, call get_sponsor_scan with the same address after a short wait. Results name brands and where their ads ran, never people or email addresses. The results_url opens the full results on bookasponsor.com.

endpoint
https://bookasponsor.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 sponsor-radar live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is sponsor-radar free to use?
Yes — the hub reached it with no key and no payment.
What tools does sponsor-radar have?
4 tools: find_newsletter_sponsors, get_sponsor_scan, get_newsletter_sponsorship_rates, list_brands_sponsoring_newsletters.
Is sponsor-radar 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
179ms

last good check

priced tools
0

of 4 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

_ what it can do 4 tools
2 open 2 never probed 2 of 4 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.

  • get_newsletter_sponsorship_rates open 1h ago

    Use this when someone asks how much to charge for a newsletter sponsorship or what newsletters charge for an ad. Returns the median price newsletters list for the main sponsor slot of one issue, by list size, read from their own advertise pages.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "subscribers": {
      "type": "integer",
      "maximum": 100000000,
      "description": "The newsletter's subscriber count, to pick its size band",
      "exclusiveMinimum": 0
    }
  }
}
    arguments 12 lines
  • list_brands_sponsoring_newsletters open 1h ago

    Use this when someone asks which companies or brands sponsor newsletters, overall or in a topic such as AI, finance or marketing. Returns the brands seen in the most newsletters in the last 12 months, read from published issues.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "niche": {
      "enum": [
        "ai",
        "business",
        "finance",
        "tech",
        "marketing",
        "health",
        "culture",
        "food",
        "productivity",
        "crypto",
        "dev",
        "design",
        "science",
        "education",
        "sports",
        "climate",
        "media",
        "local",
        "legal",
        "travel"
      ],
      "type": "string",
      "description": "Newsletter topic: ai, business, finance, tech, marketing, health, culture, food, productivity, crypto, dev, design, science, education, sports, climate, media, local, legal, travel. Leave out for all newsletters."
    }
  }
}
    arguments 32 lines
  • find_newsletter_sponsors unknown never probed

    Use this when someone who runs a newsletter asks which brands might sponsor it or how to find sponsors for it. Takes the newsletter's web address, finds similar newsletters, and returns the brands that sponsored them, with the newsletters and dates where each ad ran. Starts a scan of the public newsletter pages if none exists; a new scan takes about 15 to 60 seconds.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "newsletter_url"
  ],
  "properties": {
    "newsletter_url": {
      "type": "string",
      "maxLength": 300,
      "minLength": 3,
      "description": "The newsletter's web address, such as yourname.substack.com or yournewsletter.com"
    }
  }
}
    arguments 15 lines
  • get_sponsor_scan unknown 1h ago

    Use this to read the result of a sponsor scan that find_newsletter_sponsors started, for example when it reported that the scan was still running. Takes the same newsletter web address.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "newsletter_url"
  ],
  "properties": {
    "newsletter_url": {
      "type": "string",
      "maxLength": 300,
      "minLength": 3,
      "description": "The newsletter's web address used for find_newsletter_sponsors"
    }
  }
}
    arguments 15 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 b3baf2de75af754c.

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

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.