Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Debriefing

REMOTE · DEBRIEFING.IO

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

Available components

+4 this week 93 Trust /100

Last scanned (20 hours ago)

Scores higher than 99% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security97
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 4458 tokens (~103/item across 43 items; 43 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 74% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 44 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 0
    • Tool “create_checkout_link” rewrote its description, which is the text the model reads security
    • Tool “create_share_link” rewrote its description, which is the text the model reads security
    • Tool “draft_positioning” rewrote its description, which is the text the model reads security
    • Tool “generate_battlecard” rewrote its description, which is the text the model reads security
    • Tool “get_plan_and_limits” rewrote its description, which is the text the model reads security
    • Tool “update_icp” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • “create_share_link” reworded the description of “expiry” cosmetic
  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://debriefing.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=debriefing.io CN=YE2,O=Let's Encrypt,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA384 6631caba9d421c8f0d5f961ad054f29cecb
SANs: debriefing.io
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of debriefing.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690 8 Verified
debriefing.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://debriefing.io/.well-known/oauth-protected-resource/mcp", scope="read write spend"

Bearer resource_metadata="https://debriefing.io/.well-known/oauth-protected-resource/mcp", scope="read write spend"
Header Value
strict-transport-security max-age=63072000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

Protected resource metadata

Document https://debriefing.io/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://debriefing.io/mcp
Authorisation server https://debriefing.io

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://debriefing.io/mcp Verified 200
http (plaintext) http://debriefing.io/mcp HTTPS enforced 301 https://debriefing.io/mcp
MCP tools · 43 exposed · ~4,342 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add_battlecard_note ~73

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.

NameTypeReqDescription
bodystringyesThe talking point, in plain text
competitor_idintegeryesAn id from list_competitors
NameTypeReqDescription
messagestringyes–
noteobject––
okbooleanyes–

No examples provided.

add_competitor ~73

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.

NameTypeReqDescription
website_urlstringyesThe competitor's website, such as https://acme.example
NameTypeReqDescription
competitorobject––
messagestringyes–
okbooleanyes–

No examples provided.

add_digest_note ~57

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

NameTypeReqDescription
bodystringyesThe talking point, in plain text
digest_idstringyesA digest id or slug from list_digests
NameTypeReqDescription
messagestringyes–
noteobject––
okbooleanyes–

No examples provided.

add_monitored_page ~83

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.

NameTypeReqDescription
competitor_idintegeryesAn id from list_competitors
urlstringyesThe full page address
NameTypeReqDescription
messagestringyes–
monitored_pagesarray––
okbooleanyes–
pageobject––

No examples provided.

add_signal_note ~69

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.

NameTypeReqDescription
bodystringyesThe talking point, in plain text
signal_idintegeryesAn id from search_signals or what_changed
NameTypeReqDescription
messagestringyes–
noteobject––
okbooleanyes–

No examples provided.

create_checkout_link ~237

Creates a Stripe Checkout link that buys one Debriefing plan for this workspace. It charges nothing. The admin opens the link in a browser, checks the price, and pays there. Give the link to the person; never complete the payment for them. The link expires after 24 hours. A new customer gets a 3-day free trial: Stripe takes a card, charges nothing for 3 days, then charges the plan price unless the person cancels. A repeat customer pays at once. The first payment has a 14-day money-back guarantee, once per customer. Admin only. Send an idempotency_key. A retry with the same idempotency_key returns the first answer and does not act again.

NameTypeReqDescription
idempotency_keystringyesA unique string you make for this request, such as a UUID. Send the same key when you retry, and Debriefing returns the first answer instead of acting twice.
intervalstring–Bill each month (the default) or each year.
planstringyesThe plan to buy. get_plan_and_limits shows the current plan.
NameTypeReqDescription
checkout_urlstring––
free_trialboolean––
intervalstring––
messagestringyes–
money_back_guaranteeboolean––
okbooleanyes–
planstring––
priceobject––
replayedboolean–True when this answer repeats an earlier call with the same idempotency_key.

No examples provided.

create_share_link ~194

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; Starter and a paused workspace allow 24 hours. Send an idempotency_key. A retry with the same idempotency_key returns the first answer and does not act again.

NameTypeReqDescription
expirystring–How long the link works. Starter and a paused workspace allow only 24h, and any other choice becomes 24h there.
idempotency_keystringyesA unique string you make for this request, such as a UUID. Send the same key when you retry, and Debriefing returns the first answer instead of acting twice.
include_notesboolean–Show the team's talking points on the public page
signal_idintegeryesAn id from search_signals or what_changed
NameTypeReqDescription
messagestringyes–
okbooleanyes–
replayedboolean–True when this answer repeats an earlier call with the same idempotency_key.
shareobject––

No examples provided.

draft_positioning ~162

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. Needs a paid plan or the free first week. Counts toward a daily cap per workspace that the Debriefing app shares. Send an idempotency_key. A retry with the same idempotency_key returns the first answer and does not act again. It starts no second job and uses no allowance or daily cap a second time.

NameTypeReqDescription
idempotency_keystringyesA unique string you make for this request, such as a UUID. Send the same key when you retry, and Debriefing returns the first answer instead of acting twice.
NameTypeReqDescription
daily_capobject––
messagestringyes–
okbooleanyes–
replayedboolean–True when this answer repeats an earlier call with the same idempotency_key.

No examples provided.

generate_battlecard ~175

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, and counts toward a daily cap per workspace that the Debriefing app shares. Send an idempotency_key. A retry with the same idempotency_key returns the first answer and does not act again. It starts no second job and uses no allowance or daily cap a second time.

NameTypeReqDescription
competitor_idintegeryesAn id from list_competitors
idempotency_keystringyesA unique string you make for this request, such as a UUID. Send the same key when you retry, and Debriefing returns the first answer instead of acting twice.
NameTypeReqDescription
competitorobject––
daily_capobject––
messagestringyes–
okbooleanyes–
replayedboolean–True when this answer repeats an earlier call with the same idempotency_key.

No examples provided.

get_battlecard ~66

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

NameTypeReqDescription
battlecard_idinteger–An id from list_battlecards
competitor_idinteger–An id from list_competitors

Structured output declared, but exposes no named fields.

No examples provided.

get_company_profile ~44

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
ideal_customer_profileobjectyes–
lockedbooleanyes–
positioningobjectyes–
profileobjectyes–
urlstring––

No examples provided.

get_competitor ~76

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.

NameTypeReqDescription
competitor_idintegeryesAn id from list_competitors

Structured output declared, but exposes no named fields.

No examples provided.

get_delivery_settings ~70

Gets how often Debriefing runs a monitoring cycle for the workspace, the cadences the plan allows, and where Debriefing sends its posts. Email and Slack each get the finished cycle. Slack also gets the daily digest and each high signal alert when those switches are on. Admin only.

Input schema present but exposes no named parameters.

NameTypeReqDescription
delivery_channelsobjectyes–
monitoring_cadenceobjectyes–
urlstring––

No examples provided.

get_digest ~79

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.

NameTypeReqDescription
idstring–A digest id or slug from list_digests
typestring–A digest type, such as daily_digest

Structured output declared, but exposes no named fields.

No examples provided.

get_evidence ~51

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.

NameTypeReqDescription
signal_idintegeryesAn id from search_signals

Structured output declared, but exposes no named fields.

No examples provided.

get_free_brief_link ~119

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. One email address may request 3 free briefs in 24 hours. Send the person's email, with their consent, to check that limit before you give them the link.

NameTypeReqDescription
emailstring–Optional. The email address the person will use. The answer then says how many free brief requests it has left today.
NameTypeReqDescription
connect_urlstringyes–
free_brief_urlstringyes–
pricing_urlstring––
request_limitobjectyesThe daily limit on free brief requests. With an email, also its use today.
sign_up_urlstringyes–
what_you_getstringyes–

No examples provided.

get_plan_and_limits ~105

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, which features need a paid plan, the 3-day free trial (its end and first charge), the 14-day money-back guarantee, and whether the plan is set to cancel (read only: an admin cancels in Billing). Includes the pricing link.

Input schema present but exposes no named parameters.

NameTypeReqDescription
competitor_slotsobjectyes–
daily_capsobjectyes–
featuresobjectyes–
monitoring_cadencesobject––
planobjectyes–
pricing_urlstringyes–
research_allowanceobjectyes–
share_link_expiry_choicesarray––

No examples provided.

get_public_brief ~161

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.

NameTypeReqDescription
company_slugstring–The company part of the brief URL, such as crayon
slugstring–The date part of the brief URL, such as 2026-09-28
urlstring–The brief URL, such as https://debriefing.io/briefs/crayon/2026-09-28
NameTypeReqDescription
companyobjectyes–
coverageobject––
descriptionstring––
findingsarrayyes–
free_briefobjectyes–
markdown_urlstring––
published_onstring––
sourcesarrayyes–
summaryarrayyes–
titlestringyes–
updated_onstring––
urlstringyes–

No examples provided.

get_workspace ~57

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
connectionobjectyes–
countsobject––
idintegeryes–
namestringyes–
planobjectyes–
urlstring––
website_urlstring|null––
youobject|null––

No examples provided.

invite_member ~124

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. Send an idempotency_key. A retry with the same idempotency_key returns the first answer and does not act again.

NameTypeReqDescription
emailstringyes–
idempotency_keystringyesA unique string you make for this request, such as a UUID. Send the same key when you retry, and Debriefing returns the first answer instead of acting twice.
NameTypeReqDescription
invitationobject––
messagestringyes–
okbooleanyes–
replayedboolean–True when this answer repeats an earlier call with the same idempotency_key.

No examples provided.

list_battlecards ~44

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
itemsarrayyes–

No examples provided.

list_competitors ~47

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
itemsarrayyes–

No examples provided.

list_digests ~75

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.

NameTypeReqDescription
limitinteger––
typestring–A digest type, such as daily_digest or weekly_tldr
NameTypeReqDescription
itemsarrayyes–

No examples provided.

list_members ~25

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
itemsarrayyes–
pending_invitationsarray––

No examples provided.

pin_digest ~49

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

NameTypeReqDescription
digest_idstringyesA digest id or slug from list_digests
pinnedboolean––
NameTypeReqDescription
digest_idinteger––
messagestringyes–
okbooleanyes–
pinnedboolean––

No examples provided.

pin_signal ~48

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

NameTypeReqDescription
pinnedboolean––
signal_idintegeryesAn id from search_signals or what_changed
NameTypeReqDescription
messagestringyes–
okbooleanyes–
pinnedboolean––
signal_idinteger––

No examples provided.

rate_digest ~74

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

NameTypeReqDescription
commentstring–What is missing from the digest
digest_idstringyesA digest id or slug from list_digests
scoreinteger––
NameTypeReqDescription
messagestringyes–
okbooleanyes–
ratingobject––

No examples provided.

rate_signal ~83

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

NameTypeReqDescription
commentstring––
reasonsarray–Only when useful is false
signal_idintegeryesAn id from search_signals or what_changed
usefulbooleanyes–
NameTypeReqDescription
messagestringyes–
okbooleanyes–
ratingobject––

No examples provided.

refresh_watchlist ~127

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. Send an idempotency_key. A retry with the same idempotency_key returns the first answer and does not act again. It starts no second job and uses no allowance or daily cap a second time.

NameTypeReqDescription
idempotency_keystringyesA unique string you make for this request, such as a UUID. Send the same key when you retry, and Debriefing returns the first answer instead of acting twice.
NameTypeReqDescription
messagestringyes–
okbooleanyes–
refreshobject––
replayedboolean–True when this answer repeats an earlier call with the same idempotency_key.

No examples provided.

remove_competitor ~54

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

NameTypeReqDescription
competitor_idintegeryesAn id from list_competitors
NameTypeReqDescription
competitorobject––
messagestringyes–
okbooleanyes–

No examples provided.

remove_monitored_page ~75

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

NameTypeReqDescription
competitor_idintegeryesAn id from list_competitors
page_idinteger–An id from add_monitored_page
urlstring––
NameTypeReqDescription
messagestringyes–
monitored_pagesarray––
okbooleanyes–

No examples provided.

rename_competitor ~44

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

NameTypeReqDescription
competitor_idintegeryesAn id from list_competitors
namestringyes–
NameTypeReqDescription
competitorobject––
messagestringyes–
okbooleanyes–

No examples provided.

request_free_brief ~200

Requests a free competitive brief for a person who has no Debriefing account, and returns a claim URL. Debriefing researches the company and the competitors, and emails the brief to the person. The person opens the claim URL and signs up once, with the same email, to get a workspace that holds the brief. Ask the person first: send person_consented true only after they agree. One email address gets one brief this way; a repeat returns the same claim URL.

NameTypeReqDescription
company_urlstringyesThe person's company website, such as acme.example
competitor_domainsarray–Optional. Competitor domains to research first, such as rival.example
emailstringyesThe person's work email. The brief goes there, and the person signs up with it.
person_consentedbooleanyesTrue only when the person agreed that Debriefing researches their company and emails them the brief.
NameTypeReqDescription
claim_urlstringyes–
companystring––
emailstringyes–
next_stepsstringyes–
replayedbooleanyes–
statusstringyes–

No examples provided.

research_competitor ~149

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. Send an idempotency_key. A retry with the same idempotency_key returns the first answer and does not act again. It starts no second job and uses no allowance or daily cap a second time.

NameTypeReqDescription
competitor_idintegeryesAn id from list_competitors
idempotency_keystringyesA unique string you make for this request, such as a UUID. Send the same key when you retry, and Debriefing returns the first answer instead of acting twice.
NameTypeReqDescription
messagestringyes–
okbooleanyes–
refreshobject––
replayedboolean–True when this answer repeats an earlier call with the same idempotency_key.

No examples provided.

save_signal ~55

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

NameTypeReqDescription
savedboolean––
signal_idintegeryesAn id from search_signals or what_changed
NameTypeReqDescription
messagestringyes–
okbooleanyes–
savedboolean––
signal_idinteger––

No examples provided.

search_guides ~110

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.

NameTypeReqDescription
collectionstring–Only search one part of the library
limitinteger––
querystringyesWords to find, such as battlecard or win-loss interview
NameTypeReqDescription
free_briefobjectyes–
itemsarrayyes–

No examples provided.

search_public_briefs ~134

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.

NameTypeReqDescription
companystring–A company name, slug, or domain, such as Crayon or crayon.co
limitinteger––
querystring–Words to find in the brief, such as pricing or launch
NameTypeReqDescription
briefs_urlstringyes–
free_briefobjectyes–
itemsarrayyes–

No examples provided.

search_signals ~139

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.

NameTypeReqDescription
competitor_idinteger–An id from list_competitors
limitinteger––
querystring–Words to find in the signal title or summary
severitystring––
sincestring–ISO 8601 time. Only signals after this time.
NameTypeReqDescription
itemsarrayyes–

No examples provided.

set_delivery_channels ~131

Turns delivery by email and to Slack on or off. Slack gets the finished cycle, and also the daily digest and each high signal alert when slack_digest and slack_alerts are on. Only the switches you send change. Slack needs Growth or above and a Slack connection made in the app. Channel rules for Slack are set in the app. Admin only.

NameTypeReqDescription
emailboolean––
slackboolean–Every Slack post. Off sends nothing to Slack.
slack_alertsboolean–Each high signal alert in Slack
slack_digestboolean–The daily digest in Slack
NameTypeReqDescription
delivery_channelsobject––
messagestringyes–
okbooleanyes–

No examples provided.

set_monitoring_cadence ~64

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.

NameTypeReqDescription
cadencestringyesA cadence from get_delivery_settings, such as weekly
NameTypeReqDescription
messagestringyes–
monitoring_cadenceobject––
okbooleanyes–

No examples provided.

update_company_profile ~201

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.

NameTypeReqDescription
company_sizeinteger––
company_typestring––
descriptionstring––
differentiatorsarray–Up to 12 short items
hq_countrystring––
industrystring––
market_directionstring––
market_positionstring––
namestring––
operating_regionsarray–Regions where the company sells
positioning_exclusionsarray–What the company does not do. Up to 12 short items
primary_categorystring––
self_positioningstring––
target_customerstring––
value_propositionsarray–Up to 12 short items
website_urlstring––
NameTypeReqDescription
messagestringyes–
okbooleanyes–
positioningobject––
profileobject––

No examples provided.

update_icp ~244

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. Needs a paid plan or the free first week. A change counts toward a daily cap per workspace that the Debriefing app shares. Locked while the first brief runs. Send an idempotency_key. A retry with the same idempotency_key returns the first answer and does not act again. It starts no second job and uses no allowance or daily cap a second time.

NameTypeReqDescription
buyer_rolesarray–Buyer roles
company_sizesarray–Company sizes
company_stagesarray–Company stages
customer_typesarray–Customer types
geographiesarray–Geographies
idempotency_keystringyesA unique string you make for this request, such as a UUID. Send the same key when you retry, and Debriefing returns the first answer instead of acting twice.
industriesarray–Industries
use_casesarray–Use cases
user_rolesarray–User roles
NameTypeReqDescription
daily_capobject––
ideal_customer_profileobject––
messagestringyes–
okbooleanyes–
replayedboolean–True when this answer repeats an earlier call with the same idempotency_key.

No examples provided.

what_changed ~95

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.

NameTypeReqDescription
limitinteger–The most rows of each kind
sincestringyesISO 8601 time, such as 2026-10-01T00:00:00Z
NameTypeReqDescription
battlecardsarrayyes–
digestsarrayyes–
signalsarrayyes–
sincestringyes–

No examples provided.

Install

How do I install the Debriefing MCP server?

Debriefing is a hosted endpoint at https://debriefing.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · debriefing.io

# add to Claude Code
claude mcp add --transport http io-debriefing-debriefing 'https://debriefing.io/mcp'
Common questions

What is the Debriefing MCP server?

Debriefing is an MCP server listed in the public MCP registry as io.debriefing/debriefing. Competitive intelligence: tracked competitors, evidence-backed signals, digests and battlecards. This page covers its hosted endpoint (https://debriefing.io/mcp).

Is the Debriefing MCP server safe to use?

Debriefing scores 93 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Debriefing MCP server expose?

Debriefing exposes 43 tools: get_workspace, get_plan_and_limits, create_checkout_link, list_competitors, get_competitor, and 38 more. Their descriptions and schemas cost roughly 4,342 tokens of context every time the server is loaded.

Does the Debriefing MCP server require authentication?

Yes. Debriefing asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Debriefing MCP server still maintained?

Debriefing is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.