# SetupBay (remote · setupbay.com)

Search and install ready-made setups (rules, skills, MCP configs) for AI coding agents.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `setupbay.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-setupbay-loadouts/setupbay.md), [page](https://verifymcp.io/servers/com-setupbay-loadouts/setupbay)

## Channel facts

- Endpoint: `https://setupbay.com/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-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 621 tokens (~103/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

SetupBay is a hosted endpoint at https://setupbay.com/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 com-setupbay-loadouts 'https://setupbay.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-setupbay-loadouts": {
      "url": "https://setupbay.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-setupbay-loadouts": {
      "type": "http",
      "url": "https://setupbay.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-setupbay-loadouts]
url = "https://setupbay.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-setupbay-loadouts": {
      "type": "remote",
      "url": "https://setupbay.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-setupbay-loadouts --url 'https://setupbay.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-setupbay-loadouts:
    url: "https://setupbay.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-setupbay-loadouts": {
      "Transport": "http",
      "Url": "https://setupbay.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-setupbay-loadouts -t streamable-http -u 'https://setupbay.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-setupbay-loadouts": {
      "type": "http",
      "url": "https://setupbay.com/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-11-21 (score 69, +1)

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

### 2026-11-19 (score 68, +1)

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

### 2026-11-17 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-16 (score 66)

First indexed and scored.

## MCP tools (6)

### `search_loadouts` (~182 tokens)

Search loadouts

Search SetupBay for rule/skill/MCP bundles. Ranked by relevance to `query`; filter by agent, tags (stacks such as nextjs, godot, python) or category. With no query, lists loadouts (featured and verified first).

Input parameters:

- `agent` (string): Only loadouts that support this agent
- `category` (string): Category id (see list_tags)
- `has` (string): Only loadouts containing skills, MCP configs or rules
- `limit` (integer): Max results (default 10)
- `query` (string): Free text, e.g. 'nextjs supabase auth' or 'discord bot'
- `tags` (array): All of these stacks/categories must match, e.g. ["typescript"]
- `verified_only` (boolean): Only loadouts that passed the Level 1 automated install check

### `get_loadout` (~66 tokens)

Get loadout

Metadata for one loadout: description, agent compatibility, verification and agent-test status, requirements, and the file list with roles, sizes, raw URLs and per-agent install paths.

Input parameters:

- `id` (string, required): Loadout id, e.g. nextjs-supabase-saas

### `get_loadout_file` (~83 tokens)

Get loadout file

Raw contents of one file in a loadout (path as listed by get_loadout, e.g. AGENTS.md or skills/db-migration/SKILL.md). Max 100 KB.

Input parameters:

- `id` (string, required): Loadout id, e.g. nextjs-supabase-saas
- `path` (string, required): File path within the loadout

### `get_install_instructions` (~90 tokens)

Get install instructions

Exact install steps for one loadout and agent: each file's target path in the project, its raw URL, ready-to-run curl commands, manual steps (e.g. MCP servers for agents without a project config file) and the zip URL.

Input parameters:

- `agent` (string, required): Coding agent
- `id` (string, required): Loadout id, e.g. nextjs-supabase-saas

### `list_agents` (~28 tokens)

List agents

Supported coding agents with the instructions file each reads, its skills directory and where project MCP config goes.

### `list_tags` (~33 tokens)

List tags

All tags (stacks) and categories in the catalogue, with loadout counts. Use them as search_loadouts filters.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-setupbay-loadouts/setupbay#diagnostics

## Score history

- 2026-11-21: 69
- 2026-11-20: 68
- 2026-11-19: 68
- 2026-11-18: 67
- 2026-11-17: 67
- 2026-11-16: 66

## Common questions

### What is the SetupBay MCP server?

SetupBay is an MCP server listed in the public MCP registry as com.setupbay/loadouts. Search and install ready-made setups (rules, skills, MCP configs) for AI coding agents. This page covers its hosted endpoint (https://setupbay.com/mcp).

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

SetupBay scores 69 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 SetupBay MCP server expose?

SetupBay exposes 6 tools: search_loadouts, get_loadout, get_loadout_file, get_install_instructions, list_agents, list_tags. Their descriptions and schemas cost roughly 482 tokens of context every time the server is loaded.

### Does the SetupBay MCP server require authentication?

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

### Is the SetupBay MCP server still maintained?

SetupBay is still listed as active in the MCP registry. We last reached this channel on 21 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 SetupBay MCP server?

VerifyMCP ran 12 checks on SetupBay, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about SetupBay: HTTPS. 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.

## Links

- Remote endpoint: https://setupbay.com/mcp
- Repository: https://github.com/SetupBay/loadouts
- Website: https://setupbay.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-setupbay-loadouts/setupbay.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-setupbay-loadouts/setupbay/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-setupbay-loadouts/setupbay.json
- HTML version of this page: https://verifymcp.io/servers/com-setupbay-loadouts/setupbay
