Home / MCP registry index / io.debriefing/debriefing

Debriefing

io.debriefing/debriefing in the official MCP registry. Endpoint https://debriefing.io/mcp. Source: github.com/0xrome/debriefing-mcp.

The registry describes it as: Competitive intelligence: tracked competitors, evidence-backed signals, digests and battlecards.

We read its 43 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

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

Cursor: ~/.cursor/mcp.json

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

VS Code

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

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

get_workspace get_plan_and_limits create_checkout_link list_competitors get_competitor search_signals list_digests get_digest list_battlecards get_battlecard get_evidence add_competitor rename_competitor remove_competitor add_monitored_page remove_monitored_page research_competitor refresh_watchlist pin_signal save_signal add_signal_note rate_signal pin_digest add_digest_note rate_digest generate_battlecard add_battlecard_note get_company_profile update_company_profile update_icp draft_positioning get_delivery_settings set_monitoring_cadence set_delivery_channels create_share_link list_members invite_member what_changed search_public_briefs get_public_brief search_guides get_free_brief_link request_free_brief

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-debriefing-debriefing/badge.svg)](https://lazaretto.dev/mcp-registry/io-debriefing-debriefing)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.