Hyperscale Tenant Tools
REMOTE · HYPERSCALE0.AI · SCANNED SEP 27
Hyperscale Product reads and contract operations over MCP.
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 146 tokens (~146/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 28 days we've observed: 110 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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 Hyperscale Tenant Tools MCP server?
Hyperscale Tenant Tools is a hosted endpoint at https://hyperscale0.ai/v1/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 · hyperscale0.ai
claude mcp add --transport http ai-hyperscale0-hyperscale-tenant-tools 'https://hyperscale0.ai/v1/mcp'
{
"mcpServers": {
"ai-hyperscale0-hyperscale-tenant-tools": {
"url": "https://hyperscale0.ai/v1/mcp"
}
}
} {
"servers": {
"ai-hyperscale0-hyperscale-tenant-tools": {
"type": "http",
"url": "https://hyperscale0.ai/v1/mcp"
}
}
} [mcp_servers.ai-hyperscale0-hyperscale-tenant-tools] url = "https://hyperscale0.ai/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-hyperscale0-hyperscale-tenant-tools": {
"type": "remote",
"url": "https://hyperscale0.ai/v1/mcp",
"enabled": true
}
}
} openclaw mcp add ai-hyperscale0-hyperscale-tenant-tools --url 'https://hyperscale0.ai/v1/mcp' --transport streamable-http
mcp_servers:
ai-hyperscale0-hyperscale-tenant-tools:
url: "https://hyperscale0.ai/v1/mcp" {
"McpServers": {
"ai-hyperscale0-hyperscale-tenant-tools": {
"Transport": "http",
"Url": "https://hyperscale0.ai/v1/mcp"
}
}
} assistant mcp add ai-hyperscale0-hyperscale-tenant-tools -t streamable-http -u 'https://hyperscale0.ai/v1/mcp'
{
"mcpServers": {
"ai-hyperscale0-hyperscale-tenant-tools": {
"type": "http",
"url": "https://hyperscale0.ai/v1/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.
- 27 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 26 Sept 26 0
- Endpoint reachability: not serving MCP → reachable ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 25 Sept 26 +50
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −50
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 23 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 22 Sept 26 −1
- Tool coverage: 67% → 50% ▼ functional
- Schema quality: 91 → 146 ▼ functional
- Schema quality: good → fair functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 21 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 20 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day 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 27 Sept 2026 · Probed https://hyperscale0.ai/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hyperscale0.ai | CN=WE1,O=Google Trust Services,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9f2c7791e3a971d0e1fd3d3f84effcc |
| SANs: hyperscale0.ai, status.hyperscale0.ai, *.status.hyperscale0.ai | ||||||
| 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 hyperscale0.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| hyperscale0.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="hyperscale-mcp"
Bearer realm="hyperscale-mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | base-uri 'self'; connect-src 'self'; default-src 'self'; form-action 'self'; font-src 'self' data:; frame-ancestors 'none'; frame-src 'none'; img-src 'self' data:; object-src 'none'; script-src 'self'; script-src-attr 'none'; style-src 'self' 'unsafe-inline'; style-src-attr 'unsafe-inline'; style-src-elem 'self' 'unsafe-inline' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), geolocation=(), microphone=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hyperscale0.ai/v1/mcp | Verified | 200 | |
| http (plaintext) | http://hyperscale0.ai/v1/mcp | HTTPS enforced | 301 | https://hyperscale0.ai/v1/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 →
extension_list List catalog extensions ~41
List catalog extensions.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | Maximum items to return (1-100). Defaults to 50 when omitted. |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Hyperscale Tenant Tools MCP server?
Hyperscale Tenant Tools is an MCP server listed in the public MCP registry as ai.hyperscale0/hyperscale-tenant-tools. Hyperscale Product reads and contract operations over MCP. This page covers its hosted endpoint (https://hyperscale0.ai/v1/mcp).
Is the Hyperscale Tenant Tools MCP server safe to use?
Hyperscale Tenant Tools scores 73 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 Hyperscale Tenant Tools MCP server expose?
Hyperscale Tenant Tools exposes 1 tool: extension_list. Their descriptions and schemas cost roughly 41 tokens of context every time the server is loaded.
Does the Hyperscale Tenant Tools MCP server require authentication?
Yes. Hyperscale Tenant Tools asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Hyperscale Tenant Tools MCP server still maintained?
Hyperscale Tenant Tools is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.