Sentinel Briefing

com.sentinelbriefingPublished by sentinelbriefing.comOfficial publisherv1.0.0Updated Oct 26, 2026

Strategic monitoring and public affairs intelligence: watches, sourced notes, analysed articles.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Remote MCP endpoint for Sentinel Briefing, a strategic monitoring and public affairs intelligence service covering watches, sourced notes and analysed articles.

What you can do
  • Access strategic monitoring and public affairs intelligence from Sentinel Briefing.
  • Work with watches that track topics of interest.
  • Read sourced notes and analysed articles.
  • No individual tools are listed, so exact capabilities are not documented here.
When to use it
Consider it when an assistant needs to pull in public affairs and strategic monitoring material, such as tracked watches, sourced notes or analysed articles, from Sentinel Briefing.
Requirements
A remote streamable HTTP endpoint at app.sentinelbriefing.com; OAuth authentication is required. No environment variables or headers are declared. A Sentinel Briefing account is presumably needed to authorize access.
Before you install
Access is tied to an OAuth sign-in to a third-party intelligence service, so the assistant can read whatever that account can see; review what data the service holds before connecting. Tool-level behaviour is undocumented, so verify whether any actions write or change data.

Installation

In SourceWeft

  1. Open Sentinel Briefing 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.sentinelbriefing%2Fsentinel/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": {
    "sentinel-briefing": {
      "type": "http",
      "url": "https://app.sentinelbriefing.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. v1.0.0LatestOct 21, 2026

Score

67% 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
  • 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.