xyz.loadbay/loadbay
REMOTE · LOADBAY.XYZ
Catalog of 370+ open-source AI-agent harnesses. Search, list your own, earn USDC tips via x402.
Available components
Last scanned (20 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Search and Retrieval
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1129 tokens (~188/item across 6 items; 6 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 Management92
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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
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.
- 12 Oct 26 +4
- Stability: pass → fail ▼ security
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_harness” rewrote its description, which is the text the model reads security
- Tool “list_domains” rewrote its description, which is the text the model reads security
- Tool “search_harnesses” rewrote its description, which is the text the model reads security
- Tool “support_loadbay” rewrote its description, which is the text the model reads security
- Tool “tip_harness” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “search_harnesses” changed the type of “limit”: number → integer ▼ functional
- Server version: 1.0.0 → 1.1.0 functional
- “search_harnesses” added an optional parameter “integration” cosmetic
- “search_harnesses” reworded the description of “domain” cosmetic
- “search_harnesses” reworded the description of “limit” cosmetic
- “search_harnesses” reworded the description of “query” cosmetic
- “search_harnesses” reworded the description of “trait” cosmetic
- Tool “get_harness” changed its title: Get harness details cosmetic
- Tool “list_domains” changed its title: List harness domains cosmetic
- Tool “search_harnesses” changed its title: Find agent harnesses / MCP servers cosmetic
- Tool “submit_harness” changed its title: Submit a harness to Loadbay cosmetic
- Tool “support_loadbay” changed its title: Support Loadbay (x402) cosmetic
- Tool “tip_harness” changed its title: Tip a harness author (x402) cosmetic
- 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
- 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
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
- 31 Jul 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
- 30 Jul 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
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 4 Nov 2026 · Probed https://loadbay.xyz/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.loadbay.xyz | CN=YR1,O=Let's Encrypt,C=US | 20 Oct 2026 | 18 Jan 2027 | RSA 2048 | SHA256-RSA | 6708a10915090bb6e01ff4a674891fdd23e |
| SANs: *.loadbay.xyz, loadbay.xyz | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of loadbay.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| loadbay.xyz. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://loadbay.xyz/api/mcp | Verified | 200 | |
| http (plaintext) | http://loadbay.xyz/api/mcp | HTTPS enforced | 308 | https://loadbay.xyz/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 →
get_harness Get harness details ~78
Get full details for one harness in the Loadbay catalog by slug (from search_harnesses): repo, license, stars, language, integrations, traits, summary and a shareable loadbay.xyz page. If the slug is unknown it returns the closest matches.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | the harness slug, e.g. browser-use |
No output schema declared.
No examples provided.
list_domains List harness domains ~50
List the domains (categories) in the Loadbay catalog with how many harnesses each holds. Use it to browse when the user has no specific query, then pass a domain key to search_harnesses.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_harnesses Find agent harnesses / MCP servers ~322
Find an existing MCP server, SDK or agent framework that connects an AI agent to a service or does a task, from Loadbay's curated catalog. Use this before building an integration from scratch, or whenever the user asks for a tool, plugin, MCP server or harness for something (e.g. "MCP server for Postgres", "browser automation for agents", "crypto trading bot framework", "Slack integration"). Returns matches ranked by relevance then GitHub stars, each with repo URL, license, language, integrations and traits. All filters are optional; with none it returns the most-starred harnesses.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | restrict to one domain: trading (Trading), coding (Coding & DevOps), browser (Browser & computer), productivity (Productivity), data (Data & search), social (Social & comms), health (Health), science… |
| integration | string | – | require a named integration, e.g. "GitHub", "Coinbase", "Slack" (case-insensitive) |
| limit | integer | – | max results, default 10 |
| query | string | – | what the agent needs to do or connect to, in plain words, e.g. "postgres", "stripe payments", "web scraping" |
| trait | string | – | require a trait: mcp = exposes an MCP server, oss = open source, keys = needs API keys, sandbox = runs sandboxed, guard = has guardrails |
No output schema declared.
No examples provided.
submit_harness Submit a harness to Loadbay ~312
List a new harness on Loadbay. The repo MUST be a public, open-source GitHub repository. Optionally include a USDC address to receive tips — it must also appear in the repo's loadbay.json, .github/FUNDING.yml or README.md (proof of ownership). The listing appears immediately, tagged as community-added (unverified).
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | your GitHub handle (defaults to the repo owner) |
| baseUsdcAddress | string | – | Base USDC wallet (0x…) to receive tips — must also appear in the repo's loadbay.json, .github/FUNDING.yml or README.md |
| domain | string | yes | domain key, one of: trading | coding | browser | productivity | data | social | health | science | gaming | media | robotics |
| integrations | array | – | what it connects to, e.g. ["Coinbase","Slack"] |
| language | string | – | primary language, e.g. TypeScript |
| name | string | yes | harness name, e.g. my-coinbase-harness |
| repo | string | yes | public GitHub repo URL — must be open source (have a license) |
| solanaAddress | string | – | Solana wallet (base58) to receive USDC (SPL) tips — optional, alongside or instead of Base |
| summary | string | yes | what it connects to, what tools it exposes, how an agent uses it |
| traits | array | – | capability traits |
No output schema declared.
No examples provided.
support_loadbay Support Loadbay (x402) ~87
Only when the user asks to support or donate to Loadbay. Support the Loadbay builder with a USDC tip over x402. Returns the payable endpoint — GET it with your own x402 wallet to send the tip. Loadbay never holds funds; your wallet is the payer.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | tip amount in USD (default 5); the builder receives USDC |
No output schema declared.
No examples provided.
tip_harness Tip a harness author (x402) ~102
Only when the user asks to tip or pay a harness author. Tip in USDC over x402. Returns the payable endpoint and its payment details — GET it with an x402-capable client/wallet to actually send the tip (the agent's own wallet pays; Loadbay never holds funds).
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | tip amount in USD (default 1); the author receives USDC |
| slug | string | yes | the harness slug to tip |
No output schema declared.
No examples provided.
How do I install the xyz.loadbay/loadbay MCP server?
xyz.loadbay/loadbay is a hosted endpoint at https://loadbay.xyz/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 · loadbay.xyz
claude mcp add --transport http xyz-loadbay-loadbay 'https://loadbay.xyz/api/mcp'
What is the xyz.loadbay/loadbay MCP server?
xyz.loadbay/loadbay is an MCP server listed in the public MCP registry as xyz.loadbay/loadbay. Catalog of 370+ open-source AI-agent harnesses. Search, list your own, earn USDC tips via x402. This page covers its hosted endpoint (https://loadbay.xyz/api/mcp).
Is the xyz.loadbay/loadbay MCP server safe to use?
xyz.loadbay/loadbay scores 85 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 xyz.loadbay/loadbay MCP server expose?
xyz.loadbay/loadbay exposes 6 tools: search_harnesses, get_harness, list_domains, submit_harness, tip_harness, support_loadbay. Their descriptions and schemas cost roughly 951 tokens of context every time the server is loaded.
Does the xyz.loadbay/loadbay MCP server require authentication?
No. We connected to xyz.loadbay/loadbay without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the xyz.loadbay/loadbay MCP server still maintained?
xyz.loadbay/loadbay is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.