Skip to content

In-band sleeper sentinel

by textforagents.com · remote · no sign-in to list tools · v1.0.2 · published by com.textforagents

In-band MCP sleeper sentinel — mid-session diff and quarantine inside your own client's session.

Changes · 1
CompareRegistry entry

2 tools: 1 change things and 1 only read.

Scanned Oct 22, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http in-band-sleeper-sentinel https://textforagents.com/products/in-band-sleeper-sentinel/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

2 tools

Changes things 1Claude Code: ask
  • sentinel_inspectRun the in-band sentinel over a session transcript; returns the per-(server, client) verdict and the context-safe delivered messages.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "sentinel_inspect" says "inspect": a word for reading.
    • The description's first verb is "run": a word for a change.

    What it can reach

    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe description's first sentence says "run" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    Run the in-band sentinel over a session transcript; returns the per-(server, client) verdict and the context-safe delivered messages.
Only reads 1Claude Code: allow
  • sentinel_verdictsList your stored per-(server, client) verdicts.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List your stored per-(server, client) verdicts.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Install

Pinned to version 1.0.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http in-band-sleeper-sentinel https://textforagents.com/products/in-band-sleeper-sentinel/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__in-band-sleeper-sentinel__sentinel_verdicts"
    ],
    "ask": [
      "mcp__in-band-sleeper-sentinel__sentinel_inspect"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as in-band-sleeper-sentinel. Review it before you use it.

Capability tags behind 1 rule
  • mcp__in-band-sleeper-sentinel__sentinel_inspect private-data, untrusted-input