Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SetupBay

REMOTE · SETUPBAY.COM

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

Available components

69 Trust /100

Last scanned (21 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

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 Security63
  • 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 621 tokens (~103/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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 →

Changelog

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.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 16 Nov 26 66

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://setupbay.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=setupbay.com CN=WE1,O=Google Trust Services,C=US 19 Oct 2026 17 Jan 2027 ECDSA 256 ECDSA-SHA256 37700fafa4630f5e0ec58c4e3eb604d4
SANs: setupbay.com, www.setupbay.com, *.www.setupbay.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of setupbay.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
setupbay.com. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://setupbay.com/mcp Verified 200
http (plaintext) http://setupbay.com/mcp Inconclusive 405
MCP tools · 6 exposed · ~482 tokens

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 →

Tool Tokens
get_install_instructions ~90

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.

NameTypeReqDescription
agentstringyesCoding agent
idstringyesLoadout id, e.g. nextjs-supabase-saas

No output schema declared.

No examples provided.

get_loadout ~66

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.

NameTypeReqDescription
idstringyesLoadout id, e.g. nextjs-supabase-saas

No output schema declared.

No examples provided.

get_loadout_file ~83

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.

NameTypeReqDescription
idstringyesLoadout id, e.g. nextjs-supabase-saas
pathstringyesFile path within the loadout

No output schema declared.

No examples provided.

list_agents ~28

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_tags ~33

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_loadouts ~182

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).

NameTypeReqDescription
agentstring–Only loadouts that support this agent
categorystring–Category id (see list_tags)
hasstring–Only loadouts containing skills, MCP configs or rules
limitinteger–Max results (default 10)
querystring–Free text, e.g. 'nextjs supabase auth' or 'discord bot'
tagsarray–All of these stacks/categories must match, e.g. ["typescript"]
verified_onlyboolean–Only loadouts that passed the Level 1 automated install check

No output schema declared.

No examples provided.

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.

remote · setupbay.com

# add to Claude Code
claude mcp add --transport http com-setupbay-loadouts 'https://setupbay.com/mcp'
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.