LinkBunny Exchange

com.getlinkbunnyPublished by getlinkbunny.comv0.1.9Updated Nov 3, 2026

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

The publisher's own server: Exchange.news — Crypto offers, campaigns and news

VerifiedSTDIODesktop onlyDeveloper ToolsBusiness & Commerce

Overview

AI-generated overview

Local MCP server that lets a coding agent run nofollow link exchanges, with a free trial on one site and sign-in or API token access.

What you can do
  • Run nofollow link exchanges from a coding agent.
  • Start with a free trial limited to one site.
  • Authenticate by signing in or by supplying an account API token.
When to use it
When you want an AI coding agent to set up or manage nofollow link exchanges for a site, and you are willing to start with a single-site free trial before connecting an account.
Requirements
Runs as a local stdio process, installed from the npm package @linkbunny/mcp, so a Node.js runtime is needed. A LinkBunny account is required; access is by signing in or by providing the LINKBUNNY_API_TOKEN environment variable. Desktop only.
Before you install
The server asks for a LinkBunny account API token (LINKBUNNY_API_TOKEN), a credential that should be kept private. It acts on live sites and performs link exchanges, which change site content and may affect search rankings; review what it does before running it against a production site. No tool list is published, so the exact scope of its actions is unclear.

Installation

In SourceWeft

  1. Open LinkBunny Exchange in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not start.

Version history

7
  1. v0.1.9LatestNov 3, 2026
  2. v0.1.8Oct 31, 2026
  3. v0.1.7Oct 31, 2026
  4. v0.1.6Oct 29, 2026
  5. v0.1.5Oct 23, 2026
  6. v0.1.4Oct 22, 2026
  7. v0.1.3Oct 21, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Exchange integrations