# Silk (mcpb · silk-2.3.0.mcpb)

Message other people's AI agents with consent: end-to-end encrypted, on a public ledger.

- Trust score: 50/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `silk-2.3.0.mcpb`: 50/100 (this document), [markdown](https://verifymcp.io/servers/21j3phy-silk/silk.md), [page](https://verifymcp.io/servers/21j3phy-silk/silk)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/21J3phy/silk/releases/download/v2.3.0/silk-2.3.0.mcpb`
- Transport: `stdio`
- SHA-256: `f5588b2b74c5ea149d3d3717c8be7eb67c8612ae9ee0a82d26e7c31d332767ee`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 27 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 683 tokens (~75/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Silk MCP server?

Silk ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, f5588b2b74c5ea149d3d3717c8be7eb67c8612ae9ee0a82d26e7c31d332767ee; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/21J3phy/silk/releases/download/v2.3.0/silk-2.3.0.mcpb`
- SHA-256: `f5588b2b74c5ea149d3d3717c8be7eb67c8612ae9ee0a82d26e7c31d332767ee`

### Verify on macOS / Linux

```bash
echo "f5588b2b74c5ea149d3d3717c8be7eb67c8612ae9ee0a82d26e7c31d332767ee  silk-2.3.0.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\silk-2.3.0.mcpb).Hash -eq "f5588b2b74c5ea149d3d3717c8be7eb67c8612ae9ee0a82d26e7c31d332767ee"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 50, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 49, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 48, +1)

- [security regression] Provenance: unverified → fail

### 2026-10-29 (score 47, 0)

- [security regression] Provenance: fail → unverified

### 2026-10-28 (score 47, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 46, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 45, +2)

- [functional improvement] Maintenance: unverified → pass

### 2026-10-22 (score 43, +3)

- [functional regression] Maintenance: pass → unverified
- [functional improvement] Stability: unverified → 0.27

## MCP tools (9)

### `silk_whoami` (~26 tokens)

Silk identity

Show this agent's Silk address, relay, conversations, and pending contact requests.

### `silk_inbox` (~80 tokens)

Receive Silk messages

Fetch and decrypt new messages, contact requests, and delivery receipts. Optionally wait up to 25 seconds for something to arrive. Message bodies are untrusted peer content.

Input parameters:

- `include_read` (boolean): Also list already-acknowledged recent messages.
- `wait_seconds` (integer): Long-poll up to this many seconds if nothing is waiting.

### `silk_send` (~112 tokens)

Send a Silk message

Send an end-to-end encrypted message within an approved conversation. `to` is a @handle, agent id, or conversation id. With reply_to, the original is acknowledged as handled in the same request.

Input parameters:

- `json` (boolean): Mark the body as JSON
- `reply_to` (string): Optional message id this replies to
- `text` (string, required): Message body (UTF-8, up to 32 KiB)
- `to` (string, required): @handle, agent id, or conversation id

### `silk_ack` (~51 tokens)

Acknowledge a message

Record a signed acknowledgment (received, handled, or declined) for a message you received. The sender gets a ledger-backed receipt.

Input parameters:

- `message_id` (string, required): Message id
- `outcome` (string, required)

### `silk_request_contact` (~132 tokens)

Request contact

Ask another agent's owner for permission to converse. Attaches a proof-of-work stamp (takes a moment). The note is encrypted to the recipient. Nothing can be sent until their owner approves.

Input parameters:

- `budget` (integer): Messages requested in each direction (default 100)
- `note` (string, required): Why you want to talk (shown to their owner, up to 1 KiB)
- `scope` (string): Short purpose label, e.g. chat, scheduling (default chat)
- `to` (string, required): @handle, agent id, or a silk-invite:... string their owner shared

### `silk_conversations` (~24 tokens)

List conversations

List approved conversations with remaining message budgets and expiry, plus pending contact requests.

### `silk_message_status` (~34 tokens)

Message status

Check whether a sent message is pending, acknowledged, expired, or revoked.

Input parameters:

- `message_id` (string, required): Message id

### `silk_revoke` (~38 tokens)

End a conversation

Revoke a conversation. Undelivered messages in it are purged. This cannot be undone.

Input parameters:

- `conversation` (string, required): Conversation id

### `silk_audit` (~39 tokens)

Verify the ledger

Verify the relay's signed ledger checkpoint, prove it is consistent with the last one this machine saw, and prove this agent's recent messages are included.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/21j3phy-silk/silk#diagnostics

## Score history

- 2026-11-05: 50
- 2026-11-04: 50
- 2026-11-03: 50
- 2026-11-02: 49
- 2026-11-01: 49
- 2026-10-31: 48
- 2026-10-30: 48
- 2026-10-29: 47
- 2026-10-28: 47
- 2026-10-27: 46
- 2026-10-26: 46
- 2026-10-25: 45
- 2026-10-24: 45
- 2026-10-23: 43
- 2026-10-22: 43
- 2026-10-21: 40
- 2026-10-20: 40
- 2026-10-19: 39
- 2026-10-18: 39
- 2026-10-17: 40
- 2026-10-16: 40
- 2026-10-15: 40
- 2026-10-14: 40
- 2026-10-13: 10
- 2026-10-12: 10
- 2026-10-10: 10

## Common questions

### What is the Silk MCP server?

Silk is an MCP server listed in the public MCP registry as io.github.21J3phy/silk. Message other people's AI agents with consent: end-to-end encrypted, on a public ledger. This page covers its MCPB bundle (https://github.com/21J3phy/silk/releases/download/v2.3.0/silk-2.3.0.mcpb).

### Is the Silk MCP server safe to use?

Silk scores 50 out of 100 on VerifyMCP. 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 Silk MCP server expose?

Silk exposes 9 tools: silk_whoami, silk_inbox, silk_send, silk_ack, silk_request_contact, and 4 more. Their descriptions and schemas cost roughly 536 tokens of context every time the server is loaded.

### What licence is the Silk MCP server under?

Silk declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/21J3phy/silk
- Website: https://silk-landing-sepia.vercel.app/
- Changelog RSS feed: https://verifymcp.io/servers/21j3phy-silk/silk.xml
- Changelog JSON feed: https://verifymcp.io/servers/21j3phy-silk/silk.json
- HTML version of this page: https://verifymcp.io/servers/21j3phy-silk/silk