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

bravodm

https://bravodm.com

Registry code: f05837f6772630d1

api record

BravoDM public data for creator brand deals: price a deal with the published pricing model, look up a brand's public creator program, or read published niche rate benchmarks. Read-only; no account or sign-in is involved.

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

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.

  • lookup_brand_program unknown 1h ago

    Look up one brand's public creator program: how creators apply or pitch, the program summary, what the brand sells, and the link to its BravoDM program page. Covers only the brands with public program pages at bravodm.com/brands, from the same catalog records those pages render. Pass a brand name or its BravoDM slug.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "brand"
      ],
      "properties": {
        "brand": {
          "type": "string",
          "minLength": 1,
          "description": "Brand name (for example Caraway) or slug (caraway)."
        }
      }
    }
    arguments 14 lines
  • price_deal unknown 1h ago

    Price a creator brand deal with BravoDM's published pricing model, the same model the free calculator at bravodm.com/tools/pricing-calculator runs. Two deal kinds: a posted deal (the creator posts on their own account; pass the follower band, niche, deliverable quantities, and the usage and exclusivity terms), and a content-only UGC deal (pass mode "ugc" and a ugc_tier; the creator films and the brand posts, so the price follows the creator's experience tier and never a follower count, and only the ugcVideo quantity prices). Returns the line-by-line price and the three numbers BravoDM publishes for a package: the floor, your number, and the strong ask, in USD.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "platform",
        "niche"
      ],
      "properties": {
        "live": {
          "type": "integer",
          "maximum": 50,
          "minimum": 0,
          "description": "Quantity of live deliverables."
        },
        "mode": {
          "enum": [
            "posted",
            "ugc"
          ],
          "type": "string",
          "description": "Deal kind. \"posted\" (the default) prices a deal the creator posts, off the follower band. \"ugc\" prices a content-only deal the brand posts, off the ugc_tier experience tier. Passing ugc_tier without a mode also selects the UGC path."
        },
        "niche": {
          "enum": [
            "beauty",
            "fashion",
            "fitness",
            "food",
            "travel",
            "parenting",
            "finance",
            "tech",
            "lifestyle",
            "entertainment",
            "gaming",
            "other"
          ],
          "type": "string",
          "description": "Pricing model niche key: beauty (Beauty and skincare), fashion (Fashion), fitness (Health and fitness), food (Food and drink), travel (Travel), parenting (Parenting and family), finance (Finance and business), tech (Tech and software), lifestyle (Lifestyle), entertainment (Comedy and entertainment), gaming (Gaming), other (Other)."
        },
        "usage": {
          "enum": [
            "none",
            "30d",
            "90d",
            "180d",
            "12mo",
            "forever"
          ],
          "type": "string",
          "description": "Usage rights term key: none (No usage rights), 30d (30 days), 90d (90 days), 180d (180 days), 12mo (12 months), forever (Forever). Defaults to none."
        },
        "carousel": {
          "type": "integer",
          "maximum": 50,
          "minimum": 0,
          "description": "Quantity of carousel deliverables."
        },
        "feedPost": {
          "type": "integer",
          "maximum": 50,
          "minimum": 0,
          "description": "Quantity of feedPost deliverables."
        },
        "platform": {
          "enum": [
            "instagram",
            "tiktok",
            "youtube"
          ],
          "type": "string",
          "description": "Platform the deal runs on: instagram, tiktok, or youtube."
        },
        "storySet": {
          "type": "integer",
          "maximum": 50,
          "minimum": 0,
          "description": "Quantity of storySet deliverables."
        },
        "ugcVideo": {
          "type": "integer",
          "maximum": 50,
          "minimum": 0,
          "description": "Quantity of ugcVideo deliverables."
        },
        "ugc_tier": {
          "enum": [
            "first-deals",
            "steady",
            "proven"
          ],
          "type": "string",
          "description": "UGC experience tier key (pricing model v1.1): first-deals (First deals: New to paid UGC work, building a portfolio), steady (Steady brand work: Regular paid UGC work for brands), proven (Proven performer: A track record brands ask for by name). Only read for a content-only UGC deal (mode \"ugc\"); defaults to first-deals, the calculator's own default."
        },
        "engagement": {
          "enum": [
            "lower",
            "average",
            "above",
            "way-above"
          ],
          "type": "string",
          "description": "Engagement level key: lower (Lower than most), average (About average), above (Above average), way-above (Way above average). Defaults to average."
        },
        "shortVideo": {
          "type": "integer",
          "maximum": 50,
          "minimum": 0,
          "description": "Quantity of shortVideo deliverables."
        },
        "storyFrame": {
          "type": "integer",
          "maximum": 50,
          "minimum": 0,
          "description": "Quantity of storyFrame deliverables."
        },
        "exclusivity": {
          "enum": [
            "none",
            "30d",
            "90d"
          ],
          "type": "string",
          "description": "Exclusivity term key: none (No exclusivity), 30d (30 days), 90d (90 days). Defaults to none."
        },
        "ytDedicated": {
          "type": "integer",
          "maximum": 50,
          "minimum": 0,
          "description": "Quantity of ytDedicated deliverables."
        },
        "whitelisting": {
          "type": "boolean",
          "description": "True when the brand may run the content from its own handle (whitelisting, also called Spark or partnership ads). Raises the usage line."
        },
        "follower_band": {
          "enum": [
            "under-5k",
            "5k-10k",
            "10k-25k",
            "25k-50k",
            "50k-100k",
            "100k-250k",
            "250k-500k",
            "500k-1m",
            "1m-plus"
          ],
          "type": "string",
          "description": "Follower band key from the pricing model: under-5k (Under 5k), 5k-10k (5k to 10k), 10k-25k (10k to 25k), 25k-50k (25k to 50k), 50k-100k (50k to 100k), 100k-250k (100k to 250k), 250k-500k (250k to 500k), 500k-1m (500k to 1M), 1m-plus (1M+). Required for a posted deal. A content-only UGC deal (mode \"ugc\") prices on ugc_tier instead and ignores it."
        },
        "typical_views": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 0,
          "description": "Typical views per video. Only used for YouTube pricing, where it can raise the dedicated video rate above the band base."
        },
        "ytIntegration": {
          "type": "integer",
          "maximum": 50,
          "minimum": 0,
          "description": "Quantity of ytIntegration deliverables."
        },
        "package_discount": {
          "type": "boolean",
          "description": "True to apply the model's 10 percent package discount on the content subtotal."
        }
      }
    }
    arguments 168 lines
  • rate_benchmarks unknown 1h ago

    Read the published rate table for one niche: for a creator at 25,000 followers, the floor, your number, and strong ask for one Reel, one feed post, and one Story set, plus what 90 days of usage adds on one Reel. The UGC video is priced differently: the brand posts it, so its rate follows the creator's experience tier, not followers. Its row carries the steady brand work tier and the response includes all three tiers, the figures the UGC rates guide leads with. Figures come from the same tables published at bravodm.com/rates. Pass a niche or category key such as beauty, kitchen, fitness, or tech_gadgets.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "niche"
      ],
      "properties": {
        "niche": {
          "type": "string",
          "minLength": 1,
          "description": "Niche or category key: a published table key (fashion, food, kitchen, cleaning, home, diy, tech_gadgets, apps_software, beauty, fitness, pets, family, wellness, travel, general_products) or a pricing model niche key (finance, tech, parenting, entertainment, gaming, lifestyle, other)."
        }
      }
    }
    arguments 14 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 f05837f6772630d1.

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