MCP servers › io.debriefing › debriefing

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.debriefing/debriefing

Competitive intelligence: tracked competitors, evidence-backed signals, digests and battlecards. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-10-23Topic: commerce-and-marketing · AI-classifiedPricing: paid-subscription · AI-classifiedversion 2.0.0streamable HTTP43 tools

Summary

io.debriefing/debriefing is a remote MCP server listed in the official MCP registry at version 2.0.0. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 43 tools, 0 resources and 0 prompts.

Record checks

4 of 5 record checks met · 4 do not apply

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not met: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Repository: public
Tools: 43
Described as changing data: 24 of 43 toolsAI-classified
Mainly works on: accounts and data in outside web servicesAI-classified
Topic: commerce-and-marketingAI-classified
Pricing: paid-subscriptionAI-classified
Last tested: 2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 20 tools whose name or declaration suggests they change data (create_checkout_link, add_competitor, rename_competitor, remove_competitor, add_monitored_page and 15 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.

Worth knowing before you connect it

24 tools are described as changing something (create_checkout_link, add_competitor, rename_competitor, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-10-23
Mode: read-only (no tool calls)
Latest version: 2.0.0, published 2026-10-06 (registry, as of the 2026-10-23 snapshot)
First listed version: 2026-10-06 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-23
Package and repository: checked 2026-10-22
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 2.0.0 (published 2026-10-06).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

43tools

0resources

0prompts

What it mainly works on, as our AI model read its tool descriptions: accounts and data in outside web services.

24 of 43 tools are described as changing something (creating, editing, deleting, sending or running). For 3 the reading was uncertain, so no mark is shown.

get_workspaceon 15 other serversreads or searches
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
get_plan_and_limitsreads or searches
“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,…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
create_checkout_linkon 22 other serversdoes something elsedescribed as changing data
“Creates a Stripe Checkout link that buys one Debriefing plan for this workspace.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
3 inputs, 2 required
- planstringrequired“The plan to buy.”
- intervalstring“Bill each month (the default) or each year.”
- idempotency_keystringrequired“A unique string you make for this request, such as a UUID.”
list_competitorson 6 other serversreads or searches
“Lists the competitors this Debriefing workspace tracks, with the id, name, website, and category of each.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
get_competitoron 2 other serversreads or searches
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- competitor_idintegerrequired“An id from list_competitors”
search_signalson 7 other serversreads or searches
“Searches open signals, newest first.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs
- competitor_idinteger“An id from list_competitors”
- severitystring
- querystring“Words to find in the signal title or summary”
- sincestring“ISO 8601 time.”
- limitinteger
list_digestson 3 other serversreads or searches
“Lists the digests Debriefing wrote for this workspace, newest first.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
- typestring“A digest type, such as daily_digest or weekly_tldr”
- limitinteger
get_digeston 11 other serversreads or searches
“Gets one digest by id or slug, or the newest digest when no id is given.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
- idstring“A digest id or slug from list_digests”
- typestring“A digest type, such as daily_digest”
list_battlecardsreads or searches
“Lists the battlecards Debriefing wrote for this workspace, one for each competitor that has one.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
get_battlecardreads or searches
“Gets one battlecard by competitor_id or battlecard_id.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
- competitor_idinteger“An id from list_competitors”
- battlecard_idinteger“An id from list_battlecards”
get_evidenceon 32 other serversreads or searches
“Gets the evidence behind one signal: each source excerpt with its URL and date.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- signal_idintegerrequired“An id from search_signals”
add_competitoron 3 other serverscreates or changes datadescribed as changing data
“Adds a competitor to the workspace's core watchlist from its website.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
1 input, 1 required
- website_urlstringrequired“The competitor's website, such as https://acme.example”

Show 31 more tools

rename_competitorcreates or changes datadescribed as changing data
“Changes the display name of one tracked competitor.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
2 inputs, 2 required
- competitor_idintegerrequired“An id from list_competitors”
- namestringrequired
remove_competitoron 2 other serversdeletesdescribed as changing data
“Takes one core competitor off the watchlist.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
1 input, 1 required
- competitor_idintegerrequired“An id from list_competitors”
add_monitored_pagecreates or changes datadescribed as changing data
“Asks Debriefing to watch one more page of a core competitor, such as its pricing page.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
2 inputs, 2 required
- competitor_idintegerrequired“An id from list_competitors”
- urlstringrequired“The full page address”
remove_monitored_pagedeletesdescribed as changing data
“Stops watching a page that someone added on a core competitor.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
3 inputs, 1 required
- competitor_idintegerrequired“An id from list_competitors”
- page_idinteger“An id from add_monitored_page”
- urlstring
research_competitoron 1 other serverdescribed as changing data
“Starts the first research on one core competitor that has none yet: Debriefing reads its site and outside sources.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
2 inputs, 2 required
- competitor_idintegerrequired“An id from list_competitors”
- idempotency_keystringrequired“A unique string you make for this request, such as a UUID.”
refresh_watchlistdescribed as changing data
“Refreshes the research on the core watchlist now, instead of at the next cycle.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
1 input, 1 required
- idempotency_keystringrequired“A unique string you make for this request, such as a UUID.”
pin_signalcreates or changes datadescribed as changing data
“Pins a signal for the whole team, or removes the pin with pinned false.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
2 inputs, 1 required
- signal_idintegerrequired“An id from search_signals or what_changed”
- pinnedboolean
save_signalcreates or changes datadescribed as changing data
“Saves a signal to your own saved list, or removes it with saved false.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
2 inputs, 1 required
- signal_idintegerrequired“An id from search_signals or what_changed”
- savedboolean
add_signal_notecreates or changes datadescribed as changing data
“Adds a talking point to a signal.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
2 inputs, 2 required
- signal_idintegerrequired“An id from search_signals or what_changed”
- bodystringrequired“The talking point, in plain text”
rate_signalcreates or changes datadescribed as changing data
“Tells Debriefing whether a signal was useful to you.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
4 inputs, 2 required
- signal_idintegerrequired“An id from search_signals or what_changed”
- usefulbooleanrequired
- reasonsarray“Only when useful is false”
- commentstring
pin_digestcreates or changes datadescribed as changing data
“Pins a digest for the whole team, or removes the pin with pinned false.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
2 inputs, 1 required
- digest_idstringrequired“A digest id or slug from list_digests”
- pinnedboolean
add_digest_notecreates or changes datadescribed as changing data
“Adds a talking point to a digest.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
2 inputs, 2 required
- digest_idstringrequired“A digest id or slug from list_digests”
- bodystringrequired“The talking point, in plain text”
rate_digestcreates or changes datadescribed as changing data
“Scores a digest from 1 to 5, says what is missing from it, or both.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
3 inputs, 1 required
- digest_idstringrequired“A digest id or slug from list_digests”
- scoreinteger
- commentstring“What is missing from the digest”
generate_battlecardgenerates contentdescribed as changing data
“Writes or rewrites the battlecard for one core competitor now, instead of at the next cycle.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
2 inputs, 2 required
- competitor_idintegerrequired“An id from list_competitors”
- idempotency_keystringrequired“A unique string you make for this request, such as a UUID.”
add_battlecard_notecreates or changes datadescribed as changing data
“Adds what the team knows about a core competitor that no page says.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
2 inputs, 2 required
- competitor_idintegerrequired“An id from list_competitors”
- bodystringrequired“The talking point, in plain text”
get_company_profileon 38 other serversreads or searches
“Gets the workspace's own company profile: description, category, target customer, positioning lists, and the ideal customer profile.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
update_company_profileon 2 other serverscreates or changes datadescribed as changing data
“Changes fields of the workspace's company profile.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
16 inputs
- namestring
- website_urlstring
- descriptionstring
- industrystring
- primary_categorystring
- target_customerstring
- self_positioningstring
- company_sizeinteger
- company_typestring
- hq_countrystring
- operating_regionsarray“Regions where the company sells”
- market_positionstring
- market_directionstring
- value_propositionsarray“Up to 12 short items”
- differentiatorsarray“Up to 12 short items”
- positioning_exclusionsarray“What the company does not do.”
update_icpon 1 other servercreates or changes datadescribed as changing data
“Sets the ideal customer profile, then re-reads how much each tracked competitor overlaps it.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
9 inputs, 1 required
- customer_typesarray“Customer types”
- company_sizesarray“Company sizes”
- company_stagesarray“Company stages”
- industriesarray“Industries”
- geographiesarray“Geographies”
- buyer_rolesarray“Buyer roles”
- user_rolesarray“User roles”
- use_casesarray“Use cases”
- idempotency_keystringrequired“A unique string you make for this request, such as a UUID.”
draft_positioninggenerates contentdescribed as changing data
“Reads the company's own website and drafts the empty positioning fields: value propositions, differentiators, and exclusions.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
1 input, 1 required
- idempotency_keystringrequired“A unique string you make for this request, such as a UUID.”
get_delivery_settingsreads or searches
“Gets how often Debriefing runs a monitoring cycle for the workspace, the cadences the plan allows, and where Debriefing sends its posts.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
set_monitoring_cadencecreates or changes datadescribed as changing data
“Sets how often Debriefing runs a monitoring cycle.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
1 input, 1 required
- cadencestringrequired“A cadence from get_delivery_settings, such as weekly”
set_delivery_channelscreates or changes datadescribed as changing data
“Turns delivery by email and to Slack on or off.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
4 inputs
- emailboolean
- slackboolean“Every Slack post.”
- slack_digestboolean“The daily digest in Slack”
- slack_alertsboolean“Each high signal alert in Slack”
create_share_linkon 10 other serverscreates or changes datadescribed as changing data
“Makes a public link to one signal that anyone with the address can open.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
4 inputs, 2 required
- signal_idintegerrequired“An id from search_signals or what_changed”
- expirystring“How long the link works.”
- include_notesboolean“Show the team's talking points on the public page”
- idempotency_keystringrequired“A unique string you make for this request, such as a UUID.”
list_memberson 26 other serversreads or searches
“Lists the people in the workspace with their roles.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
invite_memberon 8 other serverssends messagesdescribed as changing data
“Sends an email invitation to join the workspace as a member.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
2 inputs, 2 required
- emailstringrequired
- idempotency_keystringrequired“A unique string you make for this request, such as a UUID.”
what_changedon 18 other serversreads or searches
“Lists everything new in the workspace since a time: signals Debriefing found, digests it wrote, and battlecards it wrote or rewrote.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- sincestringrequired“ISO 8601 time, such as 2026-10-01T00:00:00Z”
- limitinteger“The most rows of each kind”
search_public_briefsreads or searches
“Searches the competitive briefs Debriefing publishes on debriefing.io about named companies, newest first.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
- querystring“Words to find in the brief, such as pricing or launch”
- companystring“A company name, slug, or domain, such as Crayon or crayon.co”
- limitinteger
get_public_briefreads or searches
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
- urlstring“The brief URL, such as https://debriefing.io/briefs/crayon/2026-09-28”
- 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”
search_guideson 99 other servers
“Searches the public competitive intelligence library on debriefing.io: how-to guides, glossary terms, tool comparisons, alternatives pages, company profiles, and market intel posts.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
- querystringrequired“Words to find, such as battlecard or win-loss interview”
- collectionstring“Only search one part of the library”
- limitinteger
get_free_brief_link
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input
- emailstring“Optional.”
request_free_brief
“Requests a free competitive brief for a person who has no Debriefing account, and returns a claim URL.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
4 inputs, 3 required
- emailstringrequired“The person's work email.”
- company_urlstringrequired“The person's company website, such as acme.example”
- competitor_domainsarray“Optional.”
- person_consentedbooleanrequired“True only when the person agreed that Debriefing researches their company and emails them the brief.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 40 tools
Says what it returns: 50% of 32 tools
States limits, defaults or errors: 35% of 40 tools
Says when to use it: 56% of 16 tools
Items covered per tool: 2.1 of 4 on average

Counted from the listing

Parameters with a description: 74% of 102
Tools with a description: 100% of 43
Typical description length: 240 characters

The tool set

Counted from the listing

Tools: 43
Size of the list: about 12,944 tokens for an agent to load (characters ÷ 4)
Naming: 43 of 43 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 40 of 43 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://debriefing.io/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

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

VS Code · .vscode/mcp.json

{
  "servers": {
    "debriefing": {
      "type": "http",
      "url": "https://debriefing.io/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"debriefing","type":"http","url":"https://debriefing.io/mcp"}'

Claude Code

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

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://debriefing.io/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint debriefing.io/mcp	Session opened	matches	our test · 2026-10-23
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-23
Repository github.com/0xrome/debriefing-mcp	Opens publicly	matches	api.github.com · 2026-10-22

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.debriefing
GitHub owner: a personal account (0xrome)

Repository: github.com/0xrome/debriefing-mcp
Stars: 0
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no
Security policy: none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-22; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-22. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.debriefing/debriefing

Answered from the data above

Is io.debriefing/debriefing safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. 24 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Is io.debriefing/debriefing free to use?

Its website (debriefing.io/pricing) describes a paid-subscription pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.

Does io.debriefing/debriefing need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.debriefing/debriefing been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can io.debriefing/debriefing do?

It lists 43 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete, send messages, generate content and do something else. We did not call any tool, so this describes the text, not the behaviour.

Can io.debriefing/debriefing change or delete data?

24 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.debriefing/debriefing publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of io.debriefing/debriefing?

In github.com/0xrome/debriefing-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

app.himalayas/mcpHimalayas Remote Jobsalso has tools that creates or changes data, deletes, generates content, does something else, reads or searches, sends messagescompare with this one
io.github.hermoso-ai/hermosoHermosoalso has tools that creates or changes data, deletes, generates content, does something else, reads or searches, sends messagescompare with this one
ai.oriiion/oriiionoriiionalso has tools that creates or changes data, deletes, generates content, does something else, reads or searches, sends messagescompare with this one
io.github.yzlee/opcmenu独行录 / opcmenualso has tools that creates or changes data, deletes, generates content, does something else, reads or searches, sends messagescompare with this one
io.github.rankcontrol/rankcontrolRankControlalso has tools that creates or changes data, deletes, generates content, reads or searches, sends messagescompare with this one
io.github.DeviceIngineering/wb-mcp-serveralso has tools that creates or changes data, deletes, generates content, reads or searches, sends messagescompare with this one

Active servers whose topic is also “commerce-and-marketing” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 12

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 3

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
696 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 43 tools, 0 resources, 0 prompts.
3,320 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

commerce-and-marketing

AI-classified · 2026-10-23

Pricing modelAI-classified

paid-subscription

read from debriefing.io/pricing · 2026-10-23

“3-day free trial, then $80/mo. 14-day money-back guarantee.”

Programming language

not stated

GitHub detects no source language in this repository (docs-only or empty)

Hosting type

remote (hosted by the publisher)

registry · 2026-10-23

MCP capability

tools

our test · 2026-10-23

Transport

streamable HTTP

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

owner: a personal account · repository age: 0–30 days · stars: 0–9

api.github.com · 2026-10-22

Maintenance

active

api.github.com · 2026-10-22

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.debriefing/debriefing: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.debriefing/debriefing

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.debriefing/debriefing)](https://protocolprobe.com/mcp/servers/io.debriefing/debriefing)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology