xyz.loadbay/loadbay
REMOTE · LOADBAY.XYZ · SCANNED SEP 20
Catalog of 370+ open-source AI-agent harnesses. Search, list your own, earn USDC tips via x402.
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 Security63
- 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 6 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 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 Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 603 tokens (~100/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 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 6 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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'
{
"mcpServers": {
"xyz-loadbay-loadbay": {
"url": "https://loadbay.xyz/api/mcp"
}
}
} {
"servers": {
"xyz-loadbay-loadbay": {
"type": "http",
"url": "https://loadbay.xyz/api/mcp"
}
}
} [mcp_servers.xyz-loadbay-loadbay] url = "https://loadbay.xyz/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyz-loadbay-loadbay": {
"type": "remote",
"url": "https://loadbay.xyz/api/mcp",
"enabled": true
}
}
} openclaw mcp add xyz-loadbay-loadbay --url 'https://loadbay.xyz/api/mcp' --transport streamable-http
mcp_servers:
xyz-loadbay-loadbay:
url: "https://loadbay.xyz/api/mcp" {
"McpServers": {
"xyz-loadbay-loadbay": {
"Transport": "http",
"Url": "https://loadbay.xyz/api/mcp"
}
}
} assistant mcp add xyz-loadbay-loadbay -t streamable-http -u 'https://loadbay.xyz/api/mcp'
{
"mcpServers": {
"xyz-loadbay-loadbay": {
"type": "http",
"url": "https://loadbay.xyz/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.
- 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 +1
- Stability: 0.97 → pass security
- 23 Aug 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.
- 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
- 27 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
- 26 Jul 26 0
First indexed and scored.
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 20 Sept 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=YR2,O=Let's Encrypt,C=US | 19 Aug 2026 | 17 Nov 2026 | RSA 2048 | SHA256-RSA | 65957a079a21e8c5bf9403a2fc520897d63 |
| SANs: *.loadbay.xyz, loadbay.xyz | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 ~35
Get full details for one harness by its slug.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | the harness slug, e.g. browser-use |
No output schema declared.
No examples provided.
list_domains ~21
List the harness domains (categories) in the Loadbay catalog.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_harnesses ~107
Search the Loadbay catalog of harnesses for AI agents. Filter by free-text query, domain, and/or capability trait.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | domain key: trading | coding | browser | productivity | data | social | health | science | gaming | media | robotics |
| limit | number | – | max results, default 20 |
| query | string | – | free-text over name, author, summary, integrations |
| trait | string | – | require a capability trait |
No output schema declared.
No examples provided.
submit_harness ~274
List a new harness on Loadbay. The repo MUST be a public, open-source GitHub repository. Optionally include a Base USDC address to receive tips. 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 — only if you want to get paid |
| 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 ~74
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 ~92
Tip a harness author 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.
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 81 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: list_domains, search_harnesses, get_harness, submit_harness, tip_harness, support_loadbay. Their descriptions and schemas cost roughly 603 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.