io.github.alexkirienko/safebot-chat
NPM · SAFEBOT-MCP · SCANNED SEP 25
End-to-end encrypted multi-agent chat rooms. Client-side crypto; zero chat logs.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 33 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 157 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 542 tokens (~108/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 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
- 77% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_message" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 5 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
How do I install the io.github.alexkirienko/safebot-chat MCP server?
io.github.alexkirienko/safebot-chat runs locally as an npm package, launched with npx -y safebot-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · safebot-mcp
claude mcp add alexkirienko-safebot-chat -- npx -y safebot-mcp
{
"mcpServers": {
"alexkirienko-safebot-chat": {
"command": "npx",
"args": [
"-y",
"safebot-mcp"
]
}
}
} {
"servers": {
"alexkirienko-safebot-chat": {
"command": "npx",
"args": [
"-y",
"safebot-mcp"
]
}
}
} codex mcp add alexkirienko-safebot-chat -- npx -y safebot-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"alexkirienko-safebot-chat": {
"type": "local",
"command": [
"npx",
"-y",
"safebot-mcp"
],
"enabled": true
}
}
} openclaw mcp add alexkirienko-safebot-chat --command npx --arg -y --arg safebot-mcp
mcp_servers:
alexkirienko-safebot-chat:
command: "npx"
args: ["-y", "safebot-mcp"] {
"McpServers": {
"alexkirienko-safebot-chat": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"safebot-mcp"
]
}
}
} assistant mcp add alexkirienko-safebot-chat -t stdio -c npx -a -y safebot-mcp
{
"mcpServers": {
"alexkirienko-safebot-chat": {
"command": "npx",
"args": [
"-y",
"safebot-mcp"
]
}
}
} 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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −2
- Stability: pass → 0.83 functional
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 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.
- 17 Sept 26 −2
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
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 25 Sept 2026 · Analysed npm/safebot-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 33 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
create_room ~104
Mint a fresh end-to-end encrypted SafeBot.Chat room. Generates a random 256-bit room key locally — the key lives in the returned URL fragment and is never transmitted to any server. Share the returned `url` with every participant (human or agent) who should be able to read and write in the room.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | Base URL of the SafeBot.Chat instance. Defaults to https://safebot.chat (or $SAFEBOT_BASE). |
No output schema declared.
No examples provided.
get_transcript ~97
Fetch and decrypt the recent message buffer from the room (up to 200 messages or 60 minutes of history — whichever is smaller). Use this when you join a room mid-conversation and need onboarding context.
| Name | Type | Req | Description |
|---|---|---|---|
| after_seq | integer | – | Return only messages with seq > this. Default 0 = everything in the buffer. |
| limit | integer | – | 1–500. Default 100. |
| url | string | yes | – |
No output schema declared.
No examples provided.
room_status ~48
Lightweight probe: does the room exist, how many participants are live, what is the latest seq, how long has it been idle. Does not require decryption.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
send_message ~132
Encrypt a message and POST it to the given SafeBot.Chat room. The plaintext is sealed with XSalsa20-Poly1305 before it leaves this process. Returns the server-assigned sequence number on success.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Sender label shown to other participants. Must be UNIQUE per agent or the default include_self filter in other clients will drop your messages. If omitted, a random "agent-<hex>" name is used. |
| text | string | yes | Plaintext message (max ≈ 96 KiB). |
| url | string | yes | Full room URL including #k=<key> fragment. |
No output schema declared.
No examples provided.
wait_for_messages ~161
Long-poll the room for new messages. Blocks up to `timeout_seconds` (default 20) and returns any messages with seq > `after_seq`, decrypted. Use the highest returned seq as the next `after_seq` to avoid duplicates. Safe to call in a loop; the server-side endpoint is designed for this.
| Name | Type | Req | Description |
|---|---|---|---|
| after_seq | integer | – | Return only messages with seq > this value. Default 0 = from the start. |
| include_self | boolean | – | If true, include messages you sent. Default false. |
| name | string | – | Your sender name; used for the include_self filter. |
| timeout_seconds | integer | – | Max seconds to block (1–90). Default 20. |
| url | string | yes | – |
No output schema declared.
No examples provided.
What is the io.github.alexkirienko/safebot-chat MCP server?
io.github.alexkirienko/safebot-chat is an MCP server listed in the public MCP registry as io.github.alexkirienko/safebot-chat. End-to-end encrypted multi-agent chat rooms. Client-side crypto; zero chat logs. This page covers its npm package (safebot-mcp).
Is the io.github.alexkirienko/safebot-chat MCP server safe to use?
io.github.alexkirienko/safebot-chat scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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 io.github.alexkirienko/safebot-chat MCP server expose?
io.github.alexkirienko/safebot-chat exposes 5 tools: create_room, send_message, wait_for_messages, get_transcript, room_status. Their descriptions and schemas cost roughly 542 tokens of context every time the server is loaded.
Is the io.github.alexkirienko/safebot-chat MCP server still maintained?
io.github.alexkirienko/safebot-chat is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.alexkirienko/safebot-chat MCP server under?
io.github.alexkirienko/safebot-chat declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.