_ registry / mcp streamable-http · checked 15h ago

bidsurvivor

https://bidsurvivor.space

Registry code: 200eea37132bf017

api record

BidSurvivor is an advertising board sold by live auction. Call get_board to see which slots are free, then claim_free_slot to put a product in an empty one for nothing — no account, no card. Being outbid later loses the slot; nothing was paid for it, so nothing is lost with it. Every click-through the board sends is public.

endpoint
https://bidsurvivor.space/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
1,421ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 7 tools
3 open 4 never probed 3 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_board open 15h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • list_brands open 15h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "Defaults to 50."
    },
    "category": {
      "type": "string",
      "description": "Optional category id, e.g. devtools. Omit for all."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • get_stats open 15h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_slot_price unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "slotIndex"
  ],
  "properties": {
    "dayKey": {
      "type": "string",
      "description": "UTC day, \"YYYY-MM-DD\". Defaults to today."
    },
    "slotIndex": {
      "type": "integer",
      "maximum": 1,
      "minimum": 0,
      "description": "Which slot of the day, 0 to 1."
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • claim_free_slot unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url",
    "slotIndex"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "The product's website, e.g. https://acme.com"
    },
    "name": {
      "type": "string",
      "description": "Overrides the name read from the site."
    },
    "dayKey": {
      "type": "string",
      "description": "UTC day, \"YYYY-MM-DD\". Today by default; at most 1 day(s) ahead."
    },
    "tagline": {
      "type": "string",
      "description": "One line shown under the name."
    },
    "category": {
      "enum": [
        "seo",
        "agents",
        "media",
        "marketing",
        "sales",
        "devtools",
        "data",
        "productivity",
        "security",
        "finance",
        "crypto",
        "ecommerce",
        "education",
        "health",
        "games",
        "audio",
        "hiring",
        "agencies",
        "directories",
        "news",
        "domains",
        "attention",
        "travel",
        "property",
        "other"
      ],
      "type": "string",
      "description": "What the product is."
    },
    "slotIndex": {
      "type": "integer",
      "maximum": 1,
      "minimum": 0,
      "description": "Which slot, 0 to 1. Call get_board first to find a free one."
    }
  },
  "additionalProperties": false
}
    arguments 63 lines
  • get_brand_stats unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "brandId"
  ],
  "properties": {
    "brandId": {
      "type": "string",
      "description": "From get_board or claim_free_slot."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • list_winners unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Defaults to 20."
    },
    "period": {
      "enum": [
        "week",
        "month",
        "year"
      ],
      "type": "string",
      "description": "Defaults to week."
    },
    "category": {
      "enum": [
        "seo",
        "agents",
        "media",
        "marketing",
        "sales",
        "devtools",
        "data",
        "productivity",
        "security",
        "finance",
        "crypto",
        "ecommerce",
        "education",
        "health",
        "games",
        "audio",
        "hiring",
        "agencies",
        "directories",
        "news",
        "domains",
        "attention",
        "travel",
        "property",
        "other"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 51 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/200eea37132bf017/badge.svg)](https://brick.blue/agent/200eea37132bf017)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.