_ registry / mcp streamable-http · checked 31m ago

cxb

https://creatorsxbrands.com

Registry code: f64f726c989e9721

api record

Creators x Brands (creatorsxbrands.com) finds real UGC creators who are a brand's customer (an ER nurse for a nurse app, an account executive for a sales tool), checked from their own bio and posts. When the user asks for creators, call find_creators right away with who their customer is, then get_job: it waits for the graded results, which usually take 1-2 minutes. Searches run on the user's CxB account: 3 free searches, no card; results are emailed to the account's address. If a tool answers sign_in_needed, show the creators it did return, give the user the signup link, and stop there;…

endpoint
https://creatorsxbrands.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 cxb live?
Yes — it answered the hub's last check (checked 31m ago). It answered 100% of checks over the last 30 days.
Is cxb free to use?
Yes — the hub reached it with no key and no payment.
What tools does cxb have?
5 tools: get_job, get_request, request_outreach, find_creators, get_account.
Is cxb 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
349ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 2 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 5 tools
1 open 4 never probed 1 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_account open 31m ago

    Free. Whether this AI is connected to a CxB account, and for which email: the plan, free searches left, the paid fair-use window and when it reopens, and the links to upgrade. Call it to confirm a new connection works, or before telling the user what they have left.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_job unknown 31m ago

    Status and results of a find_creators search on this account: exact matches only (each with the quoted evidence for every must-have, why it fits, followers, typical views, days since last post, best video and how to reach them), how many were found, and the funnel (how many were found, active and checked). While the search runs it waits up to 45 seconds for it to finish (set wait_seconds, 0-50); call it again until status is done or failed.

    mcp-tool

    {
      "type": "object",
      "required": [
        "job_id"
      ],
      "properties": {
        "job_id": {
          "type": "string"
        },
        "wait_seconds": {
          "type": "integer",
          "description": "How long to wait for a running search to finish, 0-50. Default 45 over MCP, 0 over REST."
        }
      }
    }
    arguments 15 lines
  • get_request unknown 31m ago

    Status of a request_outreach request on this account (received, quoted, accepted, reaching out, confirmed, done or declined), CxB's latest message, and the creators who said yes once there are any.

    mcp-tool

    {
      "type": "object",
      "required": [
        "request_id"
      ],
      "properties": {
        "request_id": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • request_outreach unknown never probed

    Done for you: CxB contacts creators with the brand's brief and returns who said yes, with their rates. Give the brief, a budget and a timeline; optionally a job_id from find_creators and the creator handles to start with. Needs the user's CxB account; the quote goes to its email. A person replies with a quote within a day; nothing is sent to creators until the quote is accepted. Returns a request_id.

    mcp-tool

    {
      "type": "object",
      "required": [
        "who",
        "budget",
        "timeline"
      ],
      "properties": {
        "who": {
          "type": "string",
          "description": "Who the creators should be, in plain words: \"ER nurses who work nights\", \"account executives at SaaS companies\", \"parents of kids with food allergies\"."
        },
        "must": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Requirements every match must show, e.g. [\"works nights\"]. Default: everything in `who`."
        },
        "nice": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Preferences that rank a creator higher but aren't required, e.g. [\"B2B software\"]. Moving a requirement here can multiply the matches."
        },
        "brand": {
          "type": "string",
          "description": "The brand or product name."
        },
        "notes": {
          "type": "string"
        },
        "budget": {
          "type": "string",
          "description": "e.g. \"$1,500 for 5 videos\"."
        },
        "job_id": {
          "type": "string",
          "description": "A find_creators job to draw creators from."
        },
        "country": {
          "type": "string",
          "description": "Only if the user named a country. A preference: creators there rank first, but it isn't required. To require it, add it to must (e.g. \"lives in the US\")."
        },
        "timeline": {
          "type": "string",
          "description": "e.g. \"videos live by Dec 1\"."
        },
        "followers": {
          "type": "object",
          "properties": {
            "max": {
              "type": "integer"
            },
            "min": {
              "type": "integer"
            }
          },
          "description": "Follower range. Default 1,000 to 150,000."
        },
        "platforms": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Only \"tiktok\" for now."
        },
        "product_url": {
          "type": "string",
          "description": "The product's website, if the user gave one."
        },
        "deliverables": {
          "type": "string",
          "description": "e.g. \"one 30-second TikTok each, whitelisting for 60 days\"."
        },
        "creator_handles": {
          "type": "array",
          "items": {
            "type": "string"
          }
        }
      }
    }
    arguments 84 lines
  • find_creators unknown never probed

    Starts a search for real TikTok creators who are the brand's customer, judged from their own bio and posts, active in the last 30 days, with typical views at least 0.3x followers. Only exact fits are returned, each with the quoted evidence for every must-have. Returns at once with a job_id and instant matches: creators CxB already checked that look like the brief. A fresh search graded against the exact must-haves follows, usually within 2 minutes: call get_job right away, it waits for the result. Runs on the user's CxB account (the link this AI was connected with): 3 free searches, up to 5 creators each; Solo ($27/month) and Pro ($97/month) are unlimited searches under a fair-use window (3 and 10 fresh searches every 5 hours). Without an account it returns only the creators already checked and a signup link to give the user. Out of free searches, or asking for a paid plan the account isn't on, it returns a Stripe payment link tied to the account; the plan turns on within a minute of paying. Use it when the brief is about who the creator is, not just a topic or follower count. The full list with each creator's contact is emailed to the account's address.

    mcp-tool

    {
      "type": "object",
      "required": [
        "who"
      ],
      "properties": {
        "who": {
          "type": "string",
          "description": "Who the creators should be, in plain words: \"ER nurses who work nights\", \"account executives at SaaS companies\", \"parents of kids with food allergies\"."
        },
        "must": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Requirements every match must show, e.g. [\"works nights\"]. Default: everything in `who`."
        },
        "nice": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Preferences that rank a creator higher but aren't required, e.g. [\"B2B software\"]. Moving a requirement here can multiply the matches."
        },
        "plan": {
          "enum": [
            "free",
            "solo",
            "pro"
          ],
          "type": "string",
          "description": "free (default): 3 searches per account, up to 5 creators each. solo ($27/month) and pro ($97/month): unlimited searches, fair use 3 or 10 fresh searches every 5 hours. A subscriber's searches run on their plan by themselves; pick a paid plan only when the user asked for it, and it returns the payment link for their account."
        },
        "brand": {
          "type": "string",
          "description": "The brand or product name."
        },
        "notes": {
          "type": "string"
        },
        "country": {
          "type": "string",
          "description": "Only if the user named a country. A preference: creators there rank first, but it isn't required. To require it, add it to must (e.g. \"lives in the US\")."
        },
        "followers": {
          "type": "object",
          "properties": {
            "max": {
              "type": "integer"
            },
            "min": {
              "type": "integer"
            }
          },
          "description": "Follower range. Default 1,000 to 150,000."
        },
        "platforms": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Only \"tiktok\" for now."
        },
        "max_matches": {
          "type": "integer",
          "description": "At most this many exact fits. Capped by the plan."
        },
        "product_url": {
          "type": "string",
          "description": "The product's website, if the user gave one."
        }
      }
    }
    arguments 73 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 f64f726c989e9721.

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