OnBriefing

com.onbriefingPublished by onbriefing.comOfficial publisherv0.3.0Updated Nov 7, 2026

Check creator videos (TikTok, Instagram, YouTube) against a campaign brief, with evidence per rule.

VerifiedStreamable HTTPWeb executableBusiness & CommerceMedia & Design

Overview

AI-generated overview

Remote MCP server that lets an assistant check creator videos on TikTok, Instagram and YouTube against a campaign brief, with evidence per rule.

What you can do
  • Check creator videos against a campaign brief
  • Report rule-by-rule results with supporting evidence
  • Cover TikTok, Instagram and YouTube content
  • No tool list is published, so exact actions are not documented
When to use it
Useful for marketing, influencer or brand teams that need to verify sponsored creator videos meet brief requirements and want per-rule evidence rather than a yes/no verdict.
Requirements
Remote streamable HTTP endpoint at onbriefing.com; OAuth sign-in is required. No environment variables or headers are declared.
Before you install
OAuth grants the server access tied to your account, so review the scopes requested at sign-in. It analyzes third-party social videos, which are sent to the provider for checking. No tool list is published, so confirm whether it only reads content or also changes campaign data.

Installation

In SourceWeft

  1. Open OnBriefing in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.onbriefing%2Fonbriefing/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "onbriefing": {
      "type": "http",
      "url": "https://onbriefing.com/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.3.0LatestNov 7, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.