# Bluesky (npm · @pipeworx/mcp-bluesky)

Bluesky MCP — wraps the AT Protocol API

- Trust score: 85/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 64/100, [markdown](https://verifymcp.io/servers/pipeworx-io-bluesky/bluesky-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-bluesky/bluesky-mcp)
- npm · `@pipeworx/mcp-bluesky`: 85/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-bluesky/pipeworx-mcp-bluesky.md), [page](https://verifymcp.io/servers/pipeworx-io-bluesky/pipeworx-mcp-bluesky)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-bluesky`
- Version: `0.2.1`
- Transport: `stdio`

## 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**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-bluesky).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 555 tokens (~69/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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.

## Install

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

Bluesky runs locally as an npm package, launched with npx -y @pipeworx/mcp-bluesky. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-bluesky -- npx -y @pipeworx/mcp-bluesky
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-bluesky": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-bluesky"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-bluesky": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-bluesky"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-bluesky -- npx -y @pipeworx/mcp-bluesky
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-bluesky": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-bluesky"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-bluesky --command npx --arg -y --arg @pipeworx/mcp-bluesky
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-bluesky:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-bluesky"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-bluesky": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-bluesky"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-bluesky -t stdio -c npx -a -y @pipeworx/mcp-bluesky
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-bluesky": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-bluesky"
      ]
    }
  }
}
```

## 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-05 (score 85, +1)

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

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

- [functional regression] Security disclosure: unverified → fail

### 2026-11-02 (score 83, 0)

- [functional regression] Security disclosure: fail → unverified

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

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

### 2026-10-31 (score 82, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-30 (score 67, −14)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 81)

First indexed and scored.

## MCP tools (8)

### `get_profile` (~63 tokens)

Look up a Bluesky user's profile by handle (e.g., "alice.bsky.social"). Returns display name, bio, follower/following counts, avatar, and verification status.

Input parameters:

- `handle` (string, required): Bluesky handle (e.g., alice.bsky.social)

### `get_posts` (~64 tokens)

Fetch recent posts from a Bluesky user's timeline. Returns post text, timestamps, likes, reposts, reply counts, and threaded replies.

Input parameters:

- `handle` (string, required): Bluesky handle
- `limit` (number): Number of posts (1-100, default 20)

### `search_posts` (~74 tokens)

Search Bluesky posts by keyword or phrase. Returns matching posts with author handles, timestamps, engagement metrics, and content.Requires bsky_handle and bsky_app_password in the gateway URL query params.

Input parameters:

- `limit` (number): Number of results (1-100, default 25)
- `query` (string, required): Search query

### `get_feed` (~76 tokens)

Get posts from a Bluesky feed (e.g., "discover", "what's-hot"). Returns recent posts with authors, timestamps, and engagement counts.

Input parameters:

- `feed_uri` (string): AT URI of the feed generator (default: whats-hot)
- `limit` (number): Number of posts (1-100, default 20)

### `get_followers` (~62 tokens)

Get a user's followers on Bluesky by handle. Returns follower profiles including handles, display names, bios, and follower counts.

Input parameters:

- `handle` (string, required): Bluesky handle
- `limit` (number): Number of followers (1-100, default 50)

### `get_follows` (~61 tokens)

Get accounts a Bluesky user follows by handle. Returns followed profiles with handles, display names, bios, and descriptions.

Input parameters:

- `handle` (string, required): Bluesky handle
- `limit` (number): Number of follows (1-100, default 50)

### `get_thread` (~58 tokens)

Fetch a post thread by URI. Returns the parent post and all replies in conversation order with timestamps, authors, and engagement data.

Input parameters:

- `post_uri` (string, required): AT URI of the post (at://did/app.bsky.feed.post/rkey)

### `resolve_handle` (~44 tokens)

Convert a Bluesky handle to its DID (decentralized identifier). Returns the DID for programmatic account lookups.

Input parameters:

- `handle` (string, required): Bluesky handle to resolve

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-bluesky/pipeworx-mcp-bluesky#diagnostics

## Score history

- 2026-11-05: 85
- 2026-11-04: 84
- 2026-11-03: 84
- 2026-11-02: 83
- 2026-11-01: 83
- 2026-10-31: 82
- 2026-10-30: 67
- 2026-10-29: 81

## Common questions

### What is the Bluesky MCP server?

Bluesky is an MCP server listed in the public MCP registry as io.github.pipeworx-io/bluesky. Bluesky MCP, wraps the AT Protocol API. This page covers its npm package (@pipeworx/mcp-bluesky).

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

Bluesky scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Bluesky MCP server expose?

Bluesky exposes 8 tools: get_profile, get_posts, search_posts, get_feed, get_followers, and 3 more. Their descriptions and schemas cost roughly 502 tokens of context every time the server is loaded.

### Is the Bluesky MCP server still maintained?

Bluesky is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Bluesky MCP server under?

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

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-bluesky
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-bluesky
- Repository: https://github.com/pipeworx-io/mcp-bluesky
- Website: https://pipeworx.io/packs/bluesky
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-bluesky/pipeworx-mcp-bluesky.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-bluesky/pipeworx-mcp-bluesky.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-bluesky/pipeworx-mcp-bluesky