MCP.Market

Debriefing MCP server

online · 96% uptime
by debriefing.io·io.debriefing/debriefing·v2.0.0

Competitive intelligence: tracked competitors, evidence-backed signals, digests and battlecards.

B81/100grade B
What users say
No reviews yet
Be the first
Safety scan
B81/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Debriefing yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Debriefing tools (41, 7 write)

write = sends, deletes, buys or posts
  • add_battlecard_noteFree

    Adds what the team knows about a core competitor that no page says. The next rewrite of its battlecard reads the note as framing, never as a verified fact.

  • add_competitorFree

    Adds a competitor to the workspace's core watchlist from its website. Debriefing then monitors it. Admin only. The plan sets how many core competitors fit; get_plan_and_limits shows the free slots.

  • add_digest_noteFree

    Adds a talking point to a digest. The team sees it in the workspace.

  • add_monitored_pageFree

    Asks Debriefing to watch one more page of a core competitor, such as its pricing page. Changes on it then show up as signals. Up to 10 pages per competitor. Admin only, on a paid plan.

  • add_signal_noteFree

    Adds a talking point to a signal. The team sees it in the workspace. It never appears on a public link unless the link includes notes.

  • create_share_linkwrite actionFree

    Makes a public link to one signal that anyone with the address can open. A new link replaces the old one, which stops working. The plan sets how long a link can live; the free plan and Starter allow 24 hours.

  • draft_positioningFree

    Reads the company's own website and drafts the empty positioning fields: value propositions, differentiators, and exclusions. Filled fields stay as they are. Read the result later with get_company_profile. Admin only. Counts toward a daily cap per workspace.

  • generate_battlecardwrite actionFree

    Writes or rewrites the battlecard for one core competitor now, instead of at the next cycle. It takes about a minute; read it afterwards with get_battlecard. The competitor needs finished research. Needs a paid plan or the free first week, and counts toward a daily cap per workspace.

  • get_battlecardFree

    Gets one battlecard by competitor_id or battlecard_id. Use it when the user prepares a sales call against a competitor.

  • get_company_profileFree

    Gets the workspace's own company profile: description, category, target customer, positioning lists, and the ideal customer profile. Debriefing reads every competitor move against it.

  • get_competitorFree

    Gets the dossier for one tracked competitor: company facts, the risk and opportunity it poses to this workspace, and the stored reads on positioning, product, pricing, funding, traffic, and more. Use it when the user asks about one competitor in depth.

  • get_delivery_settingsFree

    Gets how often Debriefing runs a monitoring cycle for the workspace, the cadences the plan allows, and whether a finished cycle goes out by email and to Slack. Admin only.

  • get_digestFree

    Gets one digest by id or slug, or the newest digest when no id is given. Pass type daily_digest for the newest daily digest. Use it when the user asks for the latest brief.

  • get_evidenceFree

    Gets the evidence behind one signal: each source excerpt with its URL and date. Use it when the user asks where a claim comes from.

  • get_free_brief_linkFree

    Gets the debriefing.io links where a person requests a free competitive brief about their own company and competitors, signs up for a workspace, or compares plans. It only returns links. It sends nothing and creates nothing.

  • get_plan_and_limitsFree

    Gets the workspace plan and every limit an agent runs into: competitor slots, the weekly research allowance, the daily caps on battlecards, ICP refreshes and positioning drafts, share link lifetimes, monitoring cadences, and which features need a paid plan. Includes the pricing link.

  • get_public_briefFree

    Gets one competitive brief that Debriefing published on debriefing.io: the summary, each finding with its category and date, and the numbered public sources with their URLs. Name the brief by its URL, or by company_slug and slug from search_public_briefs. With company_slug only, gets the newest brief about that company. Needs no Debriefing account.

  • get_workspaceFree

    Gets the Debriefing workspace this connection works on: its name and website, who you are in it and your role, the scopes this connection holds, and the plan. Call it first when you are not sure what you may do.

  • invite_memberwrite actionFree

    Sends an email invitation to join the workspace as a member. The invitation lasts 7 days. Inviting the same address again sends a fresh email. Admin only, on a paid plan.

  • list_battlecardsFree

    Lists the battlecards Debriefing wrote for this workspace, one for each competitor that has one. A battlecard holds talk tracks for sales calls against that competitor.

  • list_competitorsFree

    Lists the competitors this Debriefing workspace tracks, with the id, name, website, and category of each. Call it first to get the competitor_id that other tools take.

  • list_digestsFree

    Lists the digests Debriefing wrote for this workspace, newest first. A digest is a brief that sums up competitor moves over a period. Filter by type, such as daily_digest.

  • list_membersFree

    Lists the people in the workspace with their roles. An admin also sees pending invitations.

  • pin_digestFree

    Pins a digest for the whole team, or removes the pin with pinned false.

  • pin_signalFree

    Pins a signal for the whole team, or removes the pin with pinned false.

  • rate_digestFree

    Scores a digest from 1 to 5, says what is missing from it, or both. A new rating replaces your old one.

  • rate_signalFree

    Tells Debriefing whether a signal was useful to you. For not useful, add reasons and a comment. A new rating replaces your old one.

  • refresh_watchlistFree

    Refreshes the research on the core watchlist now, instead of at the next cycle. It uses one update from the weekly research allowance. Admin only.

  • remove_competitorwrite actionFree

    Takes one core competitor off the watchlist. Debriefing stops monitoring it and keeps its history. Admin only, on a paid plan.

  • remove_monitored_pagewrite actionFree

    Stops watching a page that someone added on a core competitor. Name it by page_id or url. Admin only, on a paid plan.

  • rename_competitorFree

    Changes the display name of one tracked competitor. Admin only.

  • research_competitorFree

    Starts the first research on one core competitor that has none yet: Debriefing reads its site and outside sources. It uses one update from the weekly research allowance. Admin only.

  • save_signalFree

    Saves a signal to your own saved list, or removes it with saved false. Only you see your saved signals.

  • search_guidesFree

    Searches the public competitive intelligence library on debriefing.io: how-to guides, glossary terms, tool comparisons, alternatives pages, company profiles, and market intel posts. Returns the title, a short excerpt, and the page URL of each match, best match first. Needs no Debriefing account.

  • search_public_briefsFree

    Searches the competitive briefs Debriefing publishes on debriefing.io about named companies, newest first. Each brief is dated and every finding cites a public source. Filter by words in the brief and by company name, slug, or domain. With no arguments, lists the newest briefs. Needs no Debriefing account. Returns the page URL of each brief.

  • search_signalsFree

    Searches open signals, newest first. A signal is a competitor move that Debriefing found, such as a price change or a launch, with the source evidence. Filter by competitor_id, severity (low, medium, high), a text query, or a since time. Use it when the user asks what a competitor changed.

  • set_delivery_channelsFree

    Turns delivery of a finished cycle by email and to Slack on or off. Only the channels you send change. Slack needs a paid plan and a Slack connection made in the app. Admin only.

  • set_monitoring_cadenceFree

    Sets how often Debriefing runs a monitoring cycle. The plan decides which cadences are allowed; get_delivery_settings lists them. Admin only, on a paid plan.

  • update_company_profilewrite actionFree

    Changes fields of the workspace's company profile. Only the fields you send change. The lists replace the old lists. Admin only. Locked while the first brief runs.

  • update_icpwrite actionFree

    Sets the ideal customer profile, then re-reads how much each tracked competitor overlaps it. Only the dimensions you send change; an empty list clears one. Admin only. Counts toward a daily cap per workspace. Locked while the first brief runs.

  • what_changedFree

    Lists everything new in the workspace since a time: signals Debriefing found, digests it wrote, and battlecards it wrote or rewrote. Use it to catch up, such as since the user's last visit.

Public scan report

scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it

1 high
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1027ms20/20
  • Tool poisoning41 tool descriptions checked15/15
  • Auth qualityopen endpoint exposes 7 write-action tools with no auth3/15
  • Maintenancelast push 8 days ago15/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10

Findings (1)

  • highWrite-action tools reachable without authenticationauth.open-write
Overall 81/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Debriefing compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
81/100
higher than 62% of 48,255 servers
Tools
41
the typical server has 7
Tools that change things
17%
typical: 0%. Fewer write tools means less an agent can break
Uptime
96%
of our recent checks; the typical remote server answers 100%
Response time
249 ms
faster than 55% of 30,031 servers

What its tools let an agent do: 25 read · 8 create · 5 change · 2 delete · 1 send or post

Install Debriefing in Claude Code, Cursor or VS Code

claude mcp add --transport http debriefing https://debriefing.io/mcp
Add to Cursor

What the publisher says

From the Debriefing repository's README, as published. We do not edit it. Read it on GitHub

Debriefing MCP server

Debriefing is competitive intelligence for B2B teams. It watches your competitors, finds their moves (a price change, a launch, a new hire), and backs every signal with the source evidence. This MCP server lets Claude, ChatGPT, Cursor, and any other MCP client work on a Debriefing workspace.

This repository holds the public listing for the server: this README and server.json for the official MCP Registry. The server itself is hosted. There is nothing to install or run.

  • Website: https://debriefing.io
  • Docs: https://debriefing.io/developers?tab=mcp
  • Server card: https://debriefing.io/.well-known/mcp/server-card.json

Endpoint

Auth

  • OAuth 2.1 (Claude, ChatGPT, and other OAuth clients). The person signs in to Debriefing, approves the app, and picks the scopes: read (always), write (changes that cost nothing), and spend (actions that use a plan allowance). PKCE S256, dynamic client registration, and Client ID Metadata Documents are supported. Metadata: https://debriefing.io/.well-known/oauth-authorization-server and https://debriefing.io/.well-known/oauth-protected-resource.
  • API key (other clients). Create a key in the Debriefing app and send it as Authorization: Bearer or X-API-Key: . A key acts as the admin who created it.
  • No credential. tools/list and the four public tools work without one.

Each tool checks its scope, the person's role, and the plan. A refusal comes back as isError with the link that fixes it.

Connect

Claude (claude.ai, Desktop): Settings, Connectors, Add custom connector, URL https://debriefing.io/mcp.

Claude Code:

claude mcp add --transport http debriefing https://debriefing.io/mcp

Cursor and other JSON-config clients:

{
  "mcpServers": {
    "debriefing": { "url": "https://debriefing.io/mcp" }
  }
}

ChatGPT: add https://debriefing.io/mcp as a connector in developer mode.

Tools

Public tools (no sign-in)

They read only the briefs and guides Debriefing publishes on debriefing.io.

Read tools (scope read)

Read the workspace. They change nothing.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Debriefing: common questions

Is Debriefing MCP server safe?
Mostly: it is graded B (81/100). Read the Debriefing safety report
How do I install Debriefing?
It runs remotely at debriefing.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Debriefing need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Debriefing maintained?
The last commit was 30 days ago (2026-10-05). The latest release is v2.0.0.
Is Debriefing up?
96% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Debriefing compare with other MCP servers?
safety score 81/100 (higher than 62% of 48,255 servers); tools 41 (the typical server has 7); tools that change things 17% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.