# LinkBunny Exchange (npm · @linkbunny/mcp)

Coding agents run nofollow link exchanges. Try one free on one site. Sign in or use an API token.

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

## Components

- npm · `@linkbunny/mcp`: 34/100 (this document), [markdown](https://verifymcp.io/servers/com-getlinkbunny-exchange/linkbunny-mcp.md), [page](https://verifymcp.io/servers/com-getlinkbunny-exchange/linkbunny-mcp)

## Channel facts

- Registry: `npm`
- Package: `@linkbunny/mcp`
- Version: `0.1.9`
- 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.
  - 0 of 5 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

### How do I install the LinkBunny Exchange MCP server?

LinkBunny Exchange runs locally as an npm package, launched with npx -y @linkbunny/mcp. 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 com-getlinkbunny-exchange -- npx -y @linkbunny/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-getlinkbunny-exchange": {
      "command": "npx",
      "args": [
        "-y",
        "@linkbunny/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-getlinkbunny-exchange": {
      "command": "npx",
      "args": [
        "-y",
        "@linkbunny/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-getlinkbunny-exchange -- npx -y @linkbunny/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-getlinkbunny-exchange": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@linkbunny/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-getlinkbunny-exchange --command npx --arg -y --arg @linkbunny/mcp
```

### Hermes

```yaml
mcp_servers:
  com-getlinkbunny-exchange:
    command: "npx"
    args: ["-y", "@linkbunny/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-getlinkbunny-exchange": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@linkbunny/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-getlinkbunny-exchange -t stdio -c npx -a -y @linkbunny/mcp
```

### Other

```json
{
  "mcpServers": {
    "com-getlinkbunny-exchange": {
      "command": "npx",
      "args": [
        "-y",
        "@linkbunny/mcp"
      ]
    }
  }
}
```

## 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-02 (score 34, +5)

- [security improvement] CVE-2023-54404 no longer affects this package
- [security improvement] CVE-2026-111770 no longer affects this package
- [security improvement] CVE-2026-111768 no longer affects this package
- [security improvement] CVE-2026-111771 no longer affects this package
- [security improvement] GHSA-f897-62hf-6gxq no longer affects this package
- [security improvement] Known CVEs: fail → pass
- [functional] Package version: 0.1.8 → 0.1.9

### 2026-11-01 (score 29, +6)

- [security regression] Known CVEs: unverified → fail
- [functional improvement] Dependency health: unverified → 1.00

### 2026-10-31 (score 23, −6)

- [security regression] Known CVEs: fail → unverified
- [functional regression] Dependency health: 1.00 → unverified
- [functional] Package version: 0.1.6 → 0.1.8
- [functional] Package version: 0.1.6 → 0.1.7

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

- [security regression] GHSA-f897-62hf-6gxq affects this package: high

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

- [functional] Package version: 0.1.5 → 0.1.6

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

- [security regression] CVE-2023-54404 affects this package: high

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

- [security] Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
- [security] Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
- [functional] Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
- [functional] Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.
- [functional] Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
- [functional] Package version: 0.1.4 → 0.1.5

### 2026-10-22 (score 29, +15)

- [security improvement] Malware scan: unverified → pass
- [security] Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.
- [functional] Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [functional] Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Package version: 0.1.3 → 0.1.4

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

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

## Score history

- 2026-11-05: 34
- 2026-11-04: 34
- 2026-11-03: 34
- 2026-11-02: 34
- 2026-11-01: 29
- 2026-10-31: 23
- 2026-10-30: 29
- 2026-10-29: 29
- 2026-10-28: 29
- 2026-10-27: 29
- 2026-10-26: 29
- 2026-10-25: 29
- 2026-10-24: 29
- 2026-10-23: 29
- 2026-10-22: 29
- 2026-10-21: 14

## Common questions

### What is the LinkBunny Exchange MCP server?

LinkBunny Exchange is an MCP server listed in the public MCP registry as com.getlinkbunny/exchange. Coding agents run nofollow link exchanges. Try one free on one site. Sign in or use an API token. This page covers its npm package (@linkbunny/mcp).

### Is the LinkBunny Exchange MCP server safe to use?

LinkBunny Exchange scores 34 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. 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.

### Is the LinkBunny Exchange MCP server still maintained?

LinkBunny Exchange 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 LinkBunny Exchange MCP server under?

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

### What did VerifyMCP test on the LinkBunny Exchange MCP server?

VerifyMCP ran 8 checks on LinkBunny Exchange, covering Malware scan, Known CVEs, Install scripts, Dependency health and 4 more. 6 items could not be completed, a gap on our side rather than a finding about LinkBunny Exchange: Security disclosure, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@linkbunny/mcp
- Socket report: https://socket.dev/npm/package/@linkbunny/mcp
- Website: https://getlinkbunny.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-getlinkbunny-exchange/linkbunny-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-getlinkbunny-exchange/linkbunny-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-getlinkbunny-exchange/linkbunny-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-getlinkbunny-exchange/linkbunny-mcp