BidSurvivor
REMOTE · BIDSURVIVOR.SPACE
An advertising board sold by live auction: two twelve-hour slots a day, first claim free.
Available components
Last scanned (14 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 7 Nov 2026.
Category Marketing and SEO
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 726 tokens (~103/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Stability: 0.97 → pass security
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 6 Sept 26 0
- HSTS header: fail → pass ▲ security
- Tool “list_winners” rewrote its description, which is the text the model reads security
- Schema quality: 608 → 726 ▼ functional
- New tool “list_brands” functional
- 29 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 28 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Nov 2026 · Probed https://bidsurvivor.space/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bidsurvivor.space | CN=YE2,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6a98bc2721779f33e7c0007a2f08b92a4b0 |
| SANs: bidsurvivor.space, www.bidsurvivor.space | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bidsurvivor.space. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| space. | DS published | 51168 | 13 | Verified |
| bidsurvivor.space. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://clerk.bidsurvivor.space https://*.clerk.accounts.dev https://*.clerk.com https://js.stripe.com https://*.js.stripe.com https://maps.googleapis.com https://challenges.cloudflare.com https://www.clarity.ms https://scripts.clarity.ms https://cdn.apitiny.net; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' https://clerk.bidsurvivor.space https://*.clerk.accounts.dev https://*.clerk.com https://clerk-telemetry.com https://api.stripe.com https://maps.googleapis.com https://*.clarity.ms https://*.apitiny.net; frame-src https://js.stripe.com https://*.js.stripe.com https://hooks.stripe.com https://challenges.cloudflare.com https://clerk.bidsurvivor.space https://*.clerk.accounts.dev https://www.youtube-nocookie.com https://*.apitiny.net; worker-src 'self' blob:; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none'; report-uri /api/csp-report |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), browsing-topics=(), payment=(self "https://js.stripe.com") |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bidsurvivor.space/api/mcp | Verified | 200 | |
| http (plaintext) | http://bidsurvivor.space/api/mcp | HTTPS enforced | 301 | https://bidsurvivor.space/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
claim_free_slot Claim a free slot for a product ~225
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Which slot, 0 to 1. Call get_board first to find a free one. |
| tagline | string | – | One line shown under the name. |
| url | string | yes | The product's website, e.g. https://acme.com |
No output schema declared.
No examples provided.
get_board Get the current board ~57
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_brand_stats Get what the board sent a brand ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brandId | string | yes | From get_board or claim_free_slot. |
No output schema declared.
No examples provided.
get_slot_price Get the price of one slot ~73
What it costs to take a specific slot right now: zero if nobody holds it, otherwise the amount a bid has to beat.
| Name | Type | Req | Description |
|---|---|---|---|
| dayKey | string | – | UTC day, "YYYY-MM-DD". Defaults to today. |
| slotIndex | integer | yes | Which slot of the day, 0 to 1. |
No output schema declared.
No examples provided.
get_stats Get the board's public traffic numbers ~44
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_brands List the brands that have been on the board ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category id, e.g. devtools. Omit for all. |
| limit | number | – | Defaults to 50. |
No output schema declared.
No examples provided.
list_winners List the Hall of Survivors ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | Defaults to 20. |
| period | string | – | Defaults to week. |
No output schema declared.
No examples provided.
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.
remote · bidsurvivor.space
claude mcp add --transport http space-bidsurvivor-board 'https://bidsurvivor.space/api/mcp'
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 87 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 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the BidSurvivor MCP server?
VerifyMCP ran 13 checks on BidSurvivor, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.