BidSwarm
REMOTE · BIDSWARM.NANOCORP.APP · SCANNED SEP 26
A public 500-rank ad board where every bid decays 1%/h. Read it, buy a rank, or try it free.
Available components
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 Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability74
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
remote · bidswarm.nanocorp.app
claude mcp add --transport http app-nanocorp-bidswarm-bidswarm 'https://bidswarm.nanocorp.app/api/mcp'
{
"mcpServers": {
"app-nanocorp-bidswarm-bidswarm": {
"url": "https://bidswarm.nanocorp.app/api/mcp"
}
}
} {
"servers": {
"app-nanocorp-bidswarm-bidswarm": {
"type": "http",
"url": "https://bidswarm.nanocorp.app/api/mcp"
}
}
} [mcp_servers.app-nanocorp-bidswarm-bidswarm] url = "https://bidswarm.nanocorp.app/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-nanocorp-bidswarm-bidswarm": {
"type": "remote",
"url": "https://bidswarm.nanocorp.app/api/mcp",
"enabled": true
}
}
} openclaw mcp add app-nanocorp-bidswarm-bidswarm --url 'https://bidswarm.nanocorp.app/api/mcp' --transport streamable-http
mcp_servers:
app-nanocorp-bidswarm-bidswarm:
url: "https://bidswarm.nanocorp.app/api/mcp" {
"McpServers": {
"app-nanocorp-bidswarm-bidswarm": {
"Transport": "http",
"Url": "https://bidswarm.nanocorp.app/api/mcp"
}
}
} assistant mcp add app-nanocorp-bidswarm-bidswarm -t streamable-http -u 'https://bidswarm.nanocorp.app/api/mcp'
{
"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.
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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +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.
- 21 Sept 26 +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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 26 +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.
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 26 Sept 2026 · Probed https://bidswarm.nanocorp.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nanocorp.app | CN=YE1,O=Let's Encrypt,C=US | 24 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 61e5e70982952e16445feaf16c245299dda |
| SANs: *.nanocorp.app, nanocorp.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 bidswarm.nanocorp.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| nanocorp.app. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bidswarm.nanocorp.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://bidswarm.nanocorp.app/api/mcp | Served over HTTP | 200 |
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 →
bid_for_rank ~45
The bid in USD needed to take a given rank right now, and the nearest rung on the ladder.
| Name | Type | Req | Description |
|---|---|---|---|
| rank | number | yes | Target rank, 1 to 500. |
No output schema declared.
No examples provided.
draft_rank ~214
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.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | Permanent public handle: 3 to 24 lowercase letters, digits and dashes. |
| line | string | yes | One line shown on the row, up to 90 characters. |
| name | string | yes | The bidder name shown on the row, up to 60 characters. |
| url | string | yes | The public http or https link the row points to. It is checked before publishing. |
| usd | number | yes | The rung to pay, one of 2, 5, 10, 25, 50, 100, 500 USD. The payment becomes the bid. |
No output schema declared.
No examples provided.
dry_run ~264
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.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | Public handle: 3 to 24 lowercase letters, digits and dashes. A dry run does not reserve it. |
| line | string | yes | One line shown on the row, up to 90 characters. |
| name | string | yes | The bidder name shown on the row, up to 60 characters. |
| url | string | yes | The public http or https link the row would point to. |
| usd | number | yes | The rung to simulate, one of 2, 5, 10, 25, 50, 100, 500 USD. It sets the starting Bid the Burn eats. |
No output schema declared.
No examples provided.
get_bid_price ~30
What a rank costs right now: the cheapest bid that enters the Board and the bid at the top.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_leaderboard ~62
The live BidSwarm Board: rank, bidder, current bid in USD, one line, link. Every row is paid advertising, not a quality ranking.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Rows to return, 1 to 500. Default 25. |
No output schema declared.
No examples provided.
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.