
BravoDM MCP server
Which MCP servers are BravoDM's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-30
- Registry namecom.bravodm/bravodmverified in the MCP registry
The registry name sits under bravodm.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-30
- Tools3
- Server calls itselfbravodm
- Server version1.1.0
- Protocol version2025-06-18
On 2026-10-30 the server answered initialize and tools/list without a sign-in. First answer in 844 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 5 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
- Answeredmeasuring5 of the 7 daily checks it takes to print a share
- Median first answer138 ms
- Space in an agent's context≈ 1,650 tokensthe definitions of all its tools (3), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- not sure · Track brand deals from pitch to payment on one board
- not sure · Draft polite invoice follow-ups when payment is late
- not sure · Set a rate card with packages and prices
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
price_dealPrice 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…
lookup_brand_programLook 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…
rate_benchmarksRead 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…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"bravodm": {
"type": "http",
"url": "https://bravodm.com/api/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http bravodm https://bravodm.com/api/mcpclaude.ai, ChatGPT and other clients: add https://bravodm.com/api/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.