# BidSwarm (remote · bidswarm.nanocorp.app)

A public 500-rank ad board where every bid decays 1%/h. Read it, buy a rank, or try it free.

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-26

## Components

- remote · `bidswarm.nanocorp.app`: 73/100 (this document), [markdown](https://verifymcp.io/servers/app-nanocorp-bidswarm-bidswarm/api-mcp.md), [page](https://verifymcp.io/servers/app-nanocorp-bidswarm-bidswarm/api-mcp)

## Channel facts

- Endpoint: `https://bidswarm.nanocorp.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-09-26.

- **Endpoint Security**: 51/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 748 tokens (~149/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

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

BidSwarm is a hosted endpoint at https://bidswarm.nanocorp.app/api/mcp, so there is nothing to install locally. 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 --transport http app-nanocorp-bidswarm-bidswarm 'https://bidswarm.nanocorp.app/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-nanocorp-bidswarm-bidswarm": {
      "url": "https://bidswarm.nanocorp.app/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-nanocorp-bidswarm-bidswarm": {
      "type": "http",
      "url": "https://bidswarm.nanocorp.app/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-nanocorp-bidswarm-bidswarm]
url = "https://bidswarm.nanocorp.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-nanocorp-bidswarm-bidswarm": {
      "type": "remote",
      "url": "https://bidswarm.nanocorp.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-nanocorp-bidswarm-bidswarm --url 'https://bidswarm.nanocorp.app/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-nanocorp-bidswarm-bidswarm:
    url: "https://bidswarm.nanocorp.app/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-nanocorp-bidswarm-bidswarm": {
      "Transport": "http",
      "Url": "https://bidswarm.nanocorp.app/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-nanocorp-bidswarm-bidswarm -t streamable-http -u 'https://bidswarm.nanocorp.app/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-nanocorp-bidswarm-bidswarm": {
      "type": "http",
      "url": "https://bidswarm.nanocorp.app/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-09-25 (score 73, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 72, +1)

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

### 2026-09-21 (score 71, +1)

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

### 2026-09-19 (score 70, +1)

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

### 2026-09-17 (score 69, +1)

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

### 2026-09-15 (score 68, +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-09-12 (score 67, +1)

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

### 2026-09-10 (score 66, +1)

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

## MCP tools (5)

### `get_leaderboard` (~62 tokens)

The live BidSwarm Board: rank, bidder, current bid in USD, one line, link. Every row is paid advertising, not a quality ranking.

Input parameters:

- `limit` (number): Rows to return, 1 to 500. Default 25.

### `get_bid_price` (~30 tokens)

What a rank costs right now: the cheapest bid that enters the Board and the bid at the top.

### `bid_for_rank` (~45 tokens)

The bid in USD needed to take a given rank right now, and the nearest rung on the ladder.

Input parameters:

- `rank` (number, required): Target rank, 1 to 500.

### `draft_rank` (~214 tokens)

Prepare a rank on the Board and return the payment link that publishes it. Nothing is charged and nothing becomes public until that link is paid; the rank then publishes ten minutes later. Use it only when someone has asked for a rank and knows the price. Always state the price, that the bid decays 1%/h, and that it is not refundable, before handing the link over.

Input parameters:

- `handle` (string, required): Permanent public handle: 3 to 24 lowercase letters, digits and dashes.
- `line` (string, required): One line shown on the row, up to 90 characters.
- `name` (string, required): The bidder name shown on the row, up to 60 characters.
- `url` (string, required): The public http or https link the row points to. It is checked before publishing.
- `usd` (number, required): The rung to pay, one of 2, 5, 10, 25, 50, 100, 500 USD. The payment becomes the bid.

### `dry_run` (~264 tokens)

Put a row on the Board free for 10 minutes: the real Burn, the rank it would hold, no payment and no card. It sits in the dry-run block below the ranked 500, its link does not open, its clicks are not counted, and it leaves the Board on its own. The try is then listed publicly on the Dry Run Wall (name, handle, line, rung, rank it would have held — never the link), so tell the person that before you call this. Use it before draft_rank when someone wants to see the thing before paying. One dry run per handle per day.

Input parameters:

- `handle` (string, required): Public handle: 3 to 24 lowercase letters, digits and dashes. A dry run does not reserve it.
- `line` (string, required): One line shown on the row, up to 90 characters.
- `name` (string, required): The bidder name shown on the row, up to 60 characters.
- `url` (string, required): The public http or https link the row would point to.
- `usd` (number, required): The rung to simulate, one of 2, 5, 10, 25, 50, 100, 500 USD. It sets the starting Bid the Burn eats.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-nanocorp-bidswarm-bidswarm/api-mcp#diagnostics

## Score history

- 2026-09-26: 73
- 2026-09-25: 73
- 2026-09-24: 72
- 2026-09-23: 72
- 2026-09-22: 71
- 2026-09-21: 71
- 2026-09-20: 70
- 2026-09-19: 70
- 2026-09-18: 69
- 2026-09-17: 69
- 2026-09-16: 68
- 2026-09-15: 68
- 2026-09-14: 67
- 2026-09-13: 67
- 2026-09-12: 67
- 2026-09-11: 66
- 2026-09-10: 66
- 2026-09-09: 65
- 2026-09-08: 65
- 2026-09-07: 64
- 2026-09-06: 64
- 2026-09-05: 63
- 2026-09-04: 63
- 2026-09-03: 62
- 2026-09-02: 62
- 2026-09-01: 61
- 2026-08-31: 61
- 2026-08-30: 60
- 2026-08-29: 60
- 2026-08-28: 60

## Common questions

### What is the BidSwarm MCP server?

BidSwarm is an MCP server listed in the public MCP registry as app.nanocorp.bidswarm/bidswarm. A public 500-rank ad board where every bid decays 1%/h. Read it, buy a rank, or try it free. This page covers its hosted endpoint (https://bidswarm.nanocorp.app/api/mcp).

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

BidSwarm scores 73 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 BidSwarm MCP server expose?

BidSwarm exposes 5 tools: get_leaderboard, get_bid_price, bid_for_rank, draft_rank, dry_run. Their descriptions and schemas cost roughly 615 tokens of context every time the server is loaded.

### Does the BidSwarm MCP server require authentication?

No. We connected to BidSwarm without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the BidSwarm MCP server still maintained?

BidSwarm is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://bidswarm.nanocorp.app/api/mcp
- Website: https://bidswarm.nanocorp.app/mcp
- Changelog RSS feed: https://verifymcp.io/servers/app-nanocorp-bidswarm-bidswarm/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-nanocorp-bidswarm-bidswarm/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-nanocorp-bidswarm-bidswarm/api-mcp