_ registry / mcp http-sse · checked 40m ago

sparkads

https://sparkads.dev

Registry code: 76e6123b41a10b76

api record

This server is for advertisers managing their own SparkAds slot: stats, the free-slot grid, network-wide numbers, and editing an owned creative. It is not how a consumer app displays the SparkAds carousel. That is a two-line embed -- a <script src="https://sparkads.dev/embed.js"> tag plus a <spark-ads-carousel app="YOUR_APP_ID"> element, documented at https://sparkads.dev/docs/api#embed. If asked to add or fix the carousel in a consumer app, use that embed. Never vendor the carousel's React components, its serve/track fetch logic, or its icon-resolving code into the consumer's own repository:…

endpoint
https://sparkads.dev/api/mcp/mcp
protocol
http-sse ·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 sparkads live?
Yes — it answered the hub's last check (checked 40m ago). It answered 99% of checks over the last 30 days.
Is sparkads free to use?
Yes — the hub reached it with no key and no payment.
What tools does sparkads have?
5 tools: update_creative, get_slot, list_free_slots, get_my_stats, get_network_pulse.
Is sparkads 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.4%

90 days 99.4%· all time 99.4%

latency
633ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 311 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • get ad performance stats
  • list free ad slots
  • edit an ad creative
  • get ad network stats
takes → gives
text → data
tools
4 reads1 changes data
_ 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 5 tools
4 open 1 never probed 4 of 5 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_slot reads open 17h ago

    Get the hour this advertiser holds: the UTC hour, the same hour on their target country's clock, the country itself, and the card that runs in it with its review status. Also reports whether the ad is actually live right now, which needs all three of a held hour, an approved card and a paying subscription. Read-only.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • list_free_slots reads open 40m ago

    List the UTC hours nobody has claimed yet, out of the 24 the network sells. Pass a country to also get each free hour on that country's clock and the best five ranked by local evening attention. Supported countries: GB, IE, PT, FR, DE, ES, IT, NL, BE, SE, NO, DK, PL, CH, AT, NG, FI, GR, RO, UA, EG, ZA, IL, SA, TR, RU, KE, AE, PK, IN, BD, TH, VN, ID, CN, SG, MY, PH, HK, TW, AU, JP, KR, NZ, BR, AR, US, CA, PE, CO, MX. Read-only; claiming an hour still happens on the website.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "country": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "ISO-3166 alpha-2 country code, e.g. GB or US. Adds local times and peak suggestions."
        }
      }
    }
    arguments 12 lines
  • get_my_stats reads open 40m ago

    Get this advertiser's own ad performance for the last 30 days: impressions and clicks split by day, by app in the Spark network, and by traffic source, plus every creative they own with its review status. Read-only. Scoped to the API key holder; it cannot report on anyone else.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_network_pulse reads open 40m ago

    Get the whole network's last 24 hours: total impressions, total clicks, how many apps showed the carousel, and how many of the 24 hourly slots are taken. This is the public inventory figure, the same one the SparkAds landing page prints, not this advertiser's own numbers. Read-only.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • update_creative changes data unknown never probed

    Edit this advertiser's ad card. Pass only the fields to change; anything omitted keeps its current value. WRITE TOOL, and it costs something: saving resets the card's status to 'pending', so the ad STOPS running until a person approves it again. Say that to the user and get their agreement before calling this. Caps: name 40 characters, tagline 60, one-sentence body 160, url must be https, domain must be a bare hostname like myapp.com. House style: plain words, no exclamation marks, and the sentence says what the product does rather than why it is good.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "url": {
          "type": "string",
          "maxLength": 200,
          "description": "Where the card links to. Must be https."
        },
        "body": {
          "type": "string",
          "maxLength": 160,
          "description": "One sentence saying what the product does."
        },
        "name": {
          "type": "string",
          "maxLength": 40,
          "description": "The app name shown on the card."
        },
        "domain": {
          "type": "string",
          "maxLength": 100,
          "description": "Bare hostname, e.g. myapp.com. The card takes its logo and colour from here."
        },
        "tagline": {
          "type": "string",
          "maxLength": 60,
          "description": "Four or five words, sits under the name."
        }
      }
    }
    arguments 31 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 76e6123b41a10b76.

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

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.