# BidSurvivor (remote · bidsurvivor.space)

An advertising board sold by live auction: two twelve-hour slots a day, first claim free.

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `bidsurvivor.space`: 84/100 (this document), [markdown](https://verifymcp.io/servers/space-bidsurvivor-board/api-mcp.md), [page](https://verifymcp.io/servers/space-bidsurvivor-board/api-mcp)

## Channel facts

- Endpoint: `https://bidsurvivor.space/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-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 726 tokens (~103/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 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.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

BidSurvivor is a hosted endpoint at https://bidsurvivor.space/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 space-bidsurvivor-board 'https://bidsurvivor.space/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "space-bidsurvivor-board": {
      "url": "https://bidsurvivor.space/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "space-bidsurvivor-board": {
      "type": "http",
      "url": "https://bidsurvivor.space/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.space-bidsurvivor-board]
url = "https://bidsurvivor.space/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "space-bidsurvivor-board": {
      "type": "remote",
      "url": "https://bidsurvivor.space/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add space-bidsurvivor-board --url 'https://bidsurvivor.space/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  space-bidsurvivor-board:
    url: "https://bidsurvivor.space/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "space-bidsurvivor-board": {
      "Transport": "http",
      "Url": "https://bidsurvivor.space/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add space-bidsurvivor-board -t streamable-http -u 'https://bidsurvivor.space/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "space-bidsurvivor-board": {
      "type": "http",
      "url": "https://bidsurvivor.space/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-21 (score 84, +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-19 (score 83, +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-17 (score 82, +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-14 (score 81, +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-12 (score 80, +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.

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

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

### 2026-09-08 (score 78, +1)

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

### 2026-09-06 (score 77, +3)

- [security improvement] HSTS header: fail → pass
- [security] Tool “list_winners” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 608 → 726
- [functional] New tool “list_brands”

## MCP tools (7)

### `get_board` (~57 tokens)

Get the current board

The live advertising board: 2 slots a day of 12 hours each, showing which are held, by whom, for how much, and which are free. A slot with isFree true can be claimed for nothing with claim_free_slot.

### `get_slot_price` (~73 tokens)

Get the price of one slot

What it costs to take a specific slot right now: zero if nobody holds it, otherwise the amount a bid has to beat.

Input parameters:

- `dayKey` (string): UTC day, "YYYY-MM-DD". Defaults to today.
- `slotIndex` (integer, required): Which slot of the day, 0 to 1.

### `claim_free_slot` (~225 tokens)

Claim a free slot for a product

Put a product on the board in a slot nobody holds. Costs nothing: an empty slot has no standing bid to beat, so any amount takes it, zero included. No account and no card. The name, logo and description are read from the site automatically. One free claim per registrable domain per day, and only for today or tomorrow — booking further ahead is for bidders on the site. If somebody outbids it later the slot is lost, but nothing was paid, so nothing is lost with it.

Input parameters:

- `category` (string): What the product is.
- `dayKey` (string): UTC day, "YYYY-MM-DD". Today by default; at most 1 day(s) ahead.
- `name` (string): Overrides the name read from the site.
- `slotIndex` (integer, required): Which slot, 0 to 1. Call get_board first to find a free one.
- `tagline` (string): One line shown under the name.
- `url` (string, required): The product's website, e.g. https://acme.com

### `list_brands` (~109 tokens)

List the brands that have been on the board

Every brand that has held or contested a twelve-hour advertising slot, newest attention first, optionally filtered to one category. Each row carries what the placement delivered — card opens and click-throughs — and whether the brand bid for the slot or was placed on a free one by us. Use this to find a brandId for get_brand_stats.

Input parameters:

- `category` (string): Optional category id, e.g. devtools. Omit for all.
- `limit` (number): Defaults to 50.

### `get_brand_stats` (~58 tokens)

Get what the board sent a brand

The published numbers for one brand: slots held, card opens, and click-throughs to its own site. These are the same figures anyone can read on the site.

Input parameters:

- `brandId` (string, required): From get_board or claim_free_slot.

### `list_winners` (~83 tokens)

List the Hall of Survivors

Brands that held a slot when it closed — plus whoever is leading the live slot right now — ranked by what they paid, over the last 7 days, 30 days or a year. Optionally filtered to one category.

Input parameters:

- `category` (string)
- `limit` (integer): Defaults to 20.
- `period` (string): Defaults to week.

### `get_stats` (~44 tokens)

Get the board's public traffic numbers

How much attention the board actually sends: visitors, page views, and click-throughs to brands. Published rather than claimed — this is a small board and the numbers say so.

## Diagnostics

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

## Score history

- 2026-09-21: 84
- 2026-09-20: 83
- 2026-09-19: 83
- 2026-09-18: 82
- 2026-09-17: 82
- 2026-09-16: 81
- 2026-09-15: 81
- 2026-09-14: 81
- 2026-09-13: 80
- 2026-09-12: 80
- 2026-09-11: 79
- 2026-09-10: 79
- 2026-09-09: 78
- 2026-09-08: 78
- 2026-09-07: 77
- 2026-09-06: 77
- 2026-09-05: 74
- 2026-09-04: 73
- 2026-09-03: 73
- 2026-09-02: 72
- 2026-09-01: 72
- 2026-08-31: 71
- 2026-08-30: 71
- 2026-08-29: 70
- 2026-08-28: 70

## Common questions

### What is the BidSurvivor MCP server?

BidSurvivor is an MCP server listed in the public MCP registry as space.bidsurvivor/board. An advertising board sold by live auction: two twelve-hour slots a day, first claim free. This page covers its hosted endpoint (https://bidsurvivor.space/api/mcp).

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

BidSurvivor scores 84 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 BidSurvivor MCP server expose?

BidSurvivor exposes 7 tools: get_board, get_slot_price, claim_free_slot, list_brands, get_brand_stats, and 2 more. Their descriptions and schemas cost roughly 649 tokens of context every time the server is loaded.

### Does the BidSurvivor MCP server require authentication?

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

### Is the BidSurvivor MCP server still maintained?

BidSurvivor is still listed as active in the MCP registry. We last reached this channel on 21 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://bidsurvivor.space/api/mcp
- Website: https://bidsurvivor.space/
- Changelog RSS feed: https://verifymcp.io/servers/space-bidsurvivor-board/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/space-bidsurvivor-board/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/space-bidsurvivor-board/api-mcp