basebalance.cloud — x402 RPC & MCP gateway
REMOTE · BASEBALANCE.CLOUD · SCANNED SEP 18
USDC-gated Base JSON-RPC: free 10 req/min, $0.50 per 10k. Failover, cache, /mcp, ledger.
Available components
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the basebalance.cloud — x402 RPC & MCP gateway server?
basebalance.cloud — x402 RPC & MCP gateway is a hosted endpoint at https://basebalance.cloud/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 · basebalance.cloud
claude mcp add --transport http cloud-basebalance-basebalance 'https://basebalance.cloud/mcp'
{
"mcpServers": {
"cloud-basebalance-basebalance": {
"url": "https://basebalance.cloud/mcp"
}
}
} {
"servers": {
"cloud-basebalance-basebalance": {
"type": "http",
"url": "https://basebalance.cloud/mcp"
}
}
} [mcp_servers.cloud-basebalance-basebalance] url = "https://basebalance.cloud/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cloud-basebalance-basebalance": {
"type": "remote",
"url": "https://basebalance.cloud/mcp",
"enabled": true
}
}
} openclaw mcp add cloud-basebalance-basebalance --url 'https://basebalance.cloud/mcp' --transport streamable-http
mcp_servers:
cloud-basebalance-basebalance:
url: "https://basebalance.cloud/mcp" {
"McpServers": {
"cloud-basebalance-basebalance": {
"Transport": "http",
"Url": "https://basebalance.cloud/mcp"
}
}
} assistant mcp add cloud-basebalance-basebalance -t streamable-http -u 'https://basebalance.cloud/mcp'
{
"mcpServers": {
"cloud-basebalance-basebalance": {
"type": "http",
"url": "https://basebalance.cloud/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.
- 18 Sept 26 −6
The score moved with no change recorded against any check. We would rather say so than guess.
- 17 Sept 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Sept 26 −6
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Sept 26 −5
- HTTPS: fail → pass ▲ security
- 14 Sept 26 −6
The score moved with no change recorded against any check. We would rather say so than guess.
- 12 Sept 26 0
- HSTS header: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- 8 Sept 26 −5
- HTTPS: pass → fail ▼ security
- 5 Sept 26 33
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 18 Sept 2026 · Probed https://basebalance.cloud/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=basebalance.cloud | CN=WE1,O=Google Trust Services,C=US | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 7fb0196d2a6532760eee46a0a78015c1 |
| SANs: basebalance.cloud, *.basebalance.cloud | ||||||
| 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 basebalance.cloud. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cloud. | present | 7041 | 13 | Verified |
| basebalance.cloud. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://basebalance.cloud/mcp | Unreachable | ||
| http (plaintext) | http://basebalance.cloud/mcp | HTTPS enforced |
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 →
No tool schema has been captured from this endpoint yet.
What is the basebalance.cloud — x402 RPC & MCP gateway server?
basebalance.cloud — x402 RPC & MCP gateway is listed in the public MCP registry as cloud.basebalance/basebalance. USDC-gated Base JSON-RPC: free 10 req/min, $0.50 per 10k. Failover, cache, /mcp, ledger. This page covers its hosted endpoint (https://basebalance.cloud/mcp).
Is the basebalance.cloud — x402 RPC & MCP gateway server safe to use?
basebalance.cloud — x402 RPC & MCP gateway scores 0 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.
Does the basebalance.cloud — x402 RPC & MCP gateway server require authentication?
Its publisher declares no required credentials for basebalance.cloud — x402 RPC & MCP gateway. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the basebalance.cloud — x402 RPC & MCP gateway server still maintained?
basebalance.cloud — x402 RPC & MCP gateway has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 11 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.