Priced X creators, campaigns from a goal, plan changes, mandated payment links, proof and results.
Scored across 6 tools
Each tool targets a fairly distinct concern: company context (brain_get), feedback (feedback_send), guest capabilities (guest_status), supply counts (inventory), pricing (plan_quote_guest), and audience matching (resolve_audience). The main overlap is inventory vs resolve_audience, both returning per-channel coverage counts, but descriptions distinguish network-wide vs audience-specific measurement.
All names are snake_case, which helps, but the grammatical patterns are mixed: noun_verb (brain_get, feedback_send), verb_noun (resolve_audience), a bare noun (inventory), and a compound (plan_quote_guest, guest_status). Still readable, but no predictable verb_noun convention.
Six tools is a reasonable, well-scoped set for a guest-facing distribution surface. Slightly light for the domain, but each tool earns its place and none feels redundant.
brain_get only reads company context with no set/update counterpart, and the surface repeatedly references creating a plan or campaign (which needs an account) without any tool to actually create one. Guest workflows are covered, but the lifecycle has notable dead ends.
A guest has no saved company context, so as a guest this answers the empty context (version 0, nothing confirmed) with claim, where to sign in and confirm your company in the workspace. With an account: your company context as confirmed (name, summary, audience), its version and the version history. Optionally one section.
Inputs: section.
Needs an account. A signed-in agent tells the distribution team about a problem or an idea with any API key. As a guest this sends nothing: it answers with claim, where to sign in and create a key, so the report can be sent from an account.
Inputs: kind (required), title (required), details (required), context.
No account needed. What this connection can do without a key: which tools answer now, which need an account, the guest limits, and claim, where to sign in and create a key in Developers.
Inputs: no named parameters.
No account needed. As a guest (no audience on file): how much of the network is on sale today, per channel: approved creators, posts on sale at a current price, and whether coverage is strong or thin. Counts only, never a creator's identity. resolve_audience narrows it to an audience you describe; with an account it is measured against your own audience.
Inputs: no named parameters.
No account needed. The all-in price range a brand pays per post in one format (post, quote or thread) across every creator on sale now, and that range times the number of posts you name (1 to 50), with how many creators sell that format and when the numbers were read. A guest gets 3 quotes in any 7 days from one address (quotes_left says how many remain); the next is refused with rate_limited (reason guest_quote_limit, retry_after and resets_at). A range, not a plan: a plan names creators and dates and needs an account (claim says where to sign in and create a key).
Inputs: posts, format.
No account needed for a profile you describe (product, audience, geography; at least a product or an audience): the audience segments it matches and the coverage per channel, the same check a campaign gets when it starts. Counts only, never a creator's identity. The fit for a campaign of yours (intent_id) needs an account.
Inputs: product, audience, geography.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
x402 paid content and Nib Tips with pending holds, refunds, public ledger, pricing, and reputation.
Run a UPI creator support page from chat: supporters, goals, page, share assets. No money moves.
Optional creator-support terms and private contribution receipt tools for Gateway.
Public offers, events, approved proof, FAQs, and safe checkout links.
Add one secure layer between your agents and this server.