io.github.gopalrajsuresh/covalent-bond
NPM · COVALENT-BOND · SCANNED SEP 29
Peer-to-peer, end-to-end-encrypted collaboration channel for AI coding agents over MCP.
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
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 70 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 622 tokens (~69/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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; "bond_send" 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 9 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.gopalrajsuresh/covalent-bond MCP server?
io.github.gopalrajsuresh/covalent-bond runs locally as an npm package, launched with npx -y covalent-bond. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · covalent-bond
claude mcp add gopalrajsuresh-covalent-bond -- npx -y covalent-bond
{
"mcpServers": {
"gopalrajsuresh-covalent-bond": {
"command": "npx",
"args": [
"-y",
"covalent-bond"
]
}
}
} {
"servers": {
"gopalrajsuresh-covalent-bond": {
"command": "npx",
"args": [
"-y",
"covalent-bond"
]
}
}
} codex mcp add gopalrajsuresh-covalent-bond -- npx -y covalent-bond
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"gopalrajsuresh-covalent-bond": {
"type": "local",
"command": [
"npx",
"-y",
"covalent-bond"
],
"enabled": true
}
}
} openclaw mcp add gopalrajsuresh-covalent-bond --command npx --arg -y --arg covalent-bond
mcp_servers:
gopalrajsuresh-covalent-bond:
command: "npx"
args: ["-y", "covalent-bond"] {
"McpServers": {
"gopalrajsuresh-covalent-bond": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"covalent-bond"
]
}
}
} assistant mcp add gopalrajsuresh-covalent-bond -t stdio -c npx -a -y covalent-bond
{
"mcpServers": {
"gopalrajsuresh-covalent-bond": {
"command": "npx",
"args": [
"-y",
"covalent-bond"
]
}
}
} 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.
- 29 Sept 26 0
- Stability: 0.97 → pass security
- 28 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
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Sept 26 −3
- Stability: pass → 0.80 functional
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → pass ▲ functional
- 21 Sept 26 0
- Security disclosure: pass → unverified ▼ 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 29 Sept 2026 · Analysed npm/covalent-bond@0.1.2
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 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| 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 →
bond_accept ~52
Accept a pending file transfer. File will be written to ~/.covalent/incoming/ and its content returned, wrapped in untrusted-data markers.
| Name | Type | Req | Description |
|---|---|---|---|
| transferId | string | yes | Transfer ID from the consent prompt |
No output schema declared.
No examples provided.
bond_connect ~33
Create a new Covalent Bond session and get a shareable session code. The other agent will use this code to join.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bond_decline ~41
Decline a pending file transfer. File will be discarded and sender will not be notified.
| Name | Type | Req | Description |
|---|---|---|---|
| transferId | string | yes | Transfer ID from the consent prompt |
No output schema declared.
No examples provided.
bond_end ~25
End the current Covalent Bond session and disconnect from relay. Clears all pending transfers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bond_join ~116
Join an existing Covalent Bond session using a session code (format: XXXX-XXXX-XXXX Base58, e.g., "3KPz-QR7m-8WXn"). Call this when the user provides a session code from another agent. The code is a shared secret - it authenticates the encrypted channel and is never sent to the relay.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionCode | string | yes | Session code in format XXXX-XXXX-XXXX (Base58, e.g., "3KPz-QR7m-8WXn") |
No output schema declared.
No examples provided.
bond_message ~68
Send a short encrypted text message to the connected agent (no file involved). Use this for agent-to-agent conversation: questions, context, summaries. Requires a confirmed session. Max 4000 characters.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Message text to send to the peer (max 4000 characters) |
No output schema declared.
No examples provided.
bond_send ~88
Send a file to the connected agent. File will be encrypted and delivered with an optional message. Subject to 10-second rate limit and security validation (file type whitelist, 256KB default size limit, configurable via COVALENT_MAX_FILE_KB).
| Name | Type | Req | Description |
|---|---|---|---|
| filepath | string | yes | Absolute path to file to send |
| message | string | – | Optional message to recipient explaining the file context |
No output schema declared.
No examples provided.
bond_status ~55
Get current Covalent Bond connection status: session info, handshake state, pending file transfers, and any events (incoming transfers, peer messages) that arrived since the last tool call. Call this periodically while connected to pick up incoming transfers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bond_wait ~144
Wait (long-poll) until the next event arrives from the peer (a message, incoming file, or disconnect) or until the timeout passes. Use this in a loop to hold a live conversation with the other agent: call bond_wait, react to what it returns, reply, call bond_wait again. Returns immediately if events are already queued. This costs tokens per call, so loop only during an active conversation; for idle waiting rely on desktop notifications and bond_status.
| Name | Type | Req | Description |
|---|---|---|---|
| timeoutSeconds | number | – | How long to wait before returning if nothing arrives (default 50, min 1, max 300; note some MCP clients cap tool calls at 60s) |
No output schema declared.
No examples provided.
What is the io.github.gopalrajsuresh/covalent-bond MCP server?
io.github.gopalrajsuresh/covalent-bond is an MCP server listed in the public MCP registry as io.github.gopalrajsuresh/covalent-bond. Peer-to-peer, end-to-end-encrypted collaboration channel for AI coding agents over MCP. This page covers its npm package (covalent-bond).
Is the io.github.gopalrajsuresh/covalent-bond MCP server safe to use?
io.github.gopalrajsuresh/covalent-bond scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 29 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.gopalrajsuresh/covalent-bond MCP server expose?
io.github.gopalrajsuresh/covalent-bond exposes 9 tools: bond_connect, bond_join, bond_send, bond_accept, bond_decline, and 4 more. Their descriptions and schemas cost roughly 622 tokens of context every time the server is loaded.
Is the io.github.gopalrajsuresh/covalent-bond MCP server still maintained?
io.github.gopalrajsuresh/covalent-bond is still listed as active in the MCP registry. We last reached this channel on 29 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.gopalrajsuresh/covalent-bond MCP server under?
io.github.gopalrajsuresh/covalent-bond declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.