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.

Hyperscale Tenant Tools

REMOTE · HYPERSCALE0.AI

Hyperscale Product reads and contract operations over MCP.

Available components

−16 this week 23 Trust /100

Last scanned (2 hours ago)

Scores higher than 7% of remote servers

Reachable. Last reached 22 Nov 2026.

Category E-commerce

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 Security57
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.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, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.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.

What we tested

Checks we ran (5)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (6)

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.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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.

  • 18 Nov 26 −16
    • Endpoint reachability: behind authorisation → not serving MCP ▼ security
    • Transport: unverified → fail ▼ security
    • Authorization: pass → unverified ▼ security
    • HSTS header: pass → fail ▼ security
    • Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. security
    • Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. functional
    • Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
    • Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
  • 9 Nov 26 +16
    • Endpoint reachability: not serving MCP → behind authorisation ▼ security
    • Transport: fail → unverified ▼ security
    • Authorization: unverified → pass ▲ security
    • HSTS header: fail → pass ▲ security
    • Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
    • Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
    • Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
    • Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
  • 8 Nov 26 −16
    • Endpoint reachability: behind authorisation → not serving MCP ▼ security
    • Transport: unverified → fail ▼ security
    • Authorization: pass → unverified ▼ security
    • HSTS header: pass → fail ▼ security
    • Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. security
    • Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. functional
    • Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
    • Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
  • 6 Nov 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
  • 1 Oct 26 0
    • Authorization: partial → pass ▲ security
  • 30 Sept 26 0
    • Endpoint reachability: reachable → behind authorisation ▼ security
    • Stability: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → unverified ▼ security
    • Authorization: fail → pass ▲ security
    • First check of Authorization: partial security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
  • 29 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 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
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 22 Nov 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 20 Nov 2026 18 Feb 2027 ECDSA 256 ECDSA-SHA256 3642df1b0d62ea3d0e1cd0d8a477e4f9
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. DS published 1814 8 Verified
hyperscale0.ai. No DS 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
HTTP status 522
Header Value
x-frame-options SAMEORIGIN
referrer-policy same-origin

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 HTTP error 522
http (plaintext) http://hyperscale0.ai/v1/mcp HTTPS enforced 301 https://hyperscale0.ai/v1/mcp
MCP tools · 1 exposed · ~41 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
extension_list ~41

List catalog extensions.

NameTypeReqDescription
cursorstring––
limitinteger–Maximum items to return (1-100). Defaults to 50 when omitted.

Structured output declared, but exposes no named fields.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http ai-hyperscale0-hyperscale-tenant-tools 'https://hyperscale0.ai/v1/mcp'
Common questions

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 23 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?

Its publisher declares no required credentials for Hyperscale Tenant Tools. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

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 22 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 Hyperscale Tenant Tools MCP server?

VerifyMCP ran 5 checks on Hyperscale Tenant Tools, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Hyperscale Tenant Tools: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.