io.github.aruuhii2yo/maxion-mcp-gateway
REMOTE · 5PU357JDKQC3QYNZKJVU3OKGQY0NCSIY.LAMBDA-URL.US-EAST-1.ON.AWS
CPU telemetry & benchmarking, SHA-256 hashing, AES-256-GCM storage, AI video/image via Nova.
Available components
Last scanned (6 hours ago)
Scores higher than 16% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Design and Media
Recent critical change
Authorization (10 Aug 2026). See the changelog before you install this server.
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 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. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 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
- 2 Sept 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. 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
- 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
- 21 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: zero-heat-super-compute → io.github.aruuhii2yo/maxion-mcp-gateway security
- Tool “billing_activate” rewrote its description, which is the text the model reads security
- Tool “billing_purchase” rewrote its description, which is the text the model reads security
- Tool “engine_maxion_activate” rewrote its description, which is the text the model reads security
- Tool “engine_maxion_deactivate” rewrote its description, which is the text the model reads security
- Tool “gateway_status” rewrote its description, which is the text the model reads security
- Tool “media_lineage0_generate” rewrote its description, which is the text the model reads security
- Tool “security_diamonize_logs” rewrote its description, which is the text the model reads security
- Tool “security_diamonize_quarantine” rewrote its description, which is the text the model reads security
- Tool “security_diamonize_scan” rewrote its description, which is the text the model reads security
- Tool “security_diamonize_status” rewrote its description, which is the text the model reads security
- Tool “storage_quezar_status” rewrote its description, which is the text the model reads security
- Tool “storage_quezar_store” rewrote its description, which is the text the model reads security
- Schema quality: 41 → 57 ▼ functional
- MCP protocol: fail → pass ▲ functional
- MCP protocol version: 2024-11-05 → 2025-11-25 functional
- “billing_activate” reworded the description of “license_key” cosmetic
- “billing_activate” reworded the description of “product_permalink” cosmetic
- “billing_purchase” reworded the description of “duration” cosmetic
- “media_lineage0_generate” reworded the description of “duration” cosmetic
- “media_lineage0_generate” reworded the description of “media_type” cosmetic
- “media_lineage0_generate” reworded the description of “prompt” cosmetic
- “security_diamonize_logs” reworded the description of “count” cosmetic
- “security_diamonize_quarantine” reworded the description of “target” cosmetic
- “security_diamonize_scan” reworded the description of “target” cosmetic
- “storage_quezar_delete” reworded the description of “Vault_id” cosmetic
- “storage_quezar_store” reworded the description of “payload” cosmetic
- 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
- 10 Aug 26 0
- Authorization: unverified → fail ▼ critical
- Stability: unverified → fail ▼ security
- Tool “billing.activate” was removed ▼ security
- Tool “billing.purchase” was removed ▼ security
- Tool “engine.maxion.activate” was removed ▼ security
- Tool “engine.maxion.deactivate” was removed ▼ security
- Tool “engine.maxion.diagnostics” was removed ▼ security
- Tool “engine.maxion.status” was removed ▼ security
- Tool “gateway.pair_agent” was removed ▼ security
- Tool “gateway.status” was removed ▼ security
- Tool “media.lineage0.archive” was removed ▼ security
- Tool “media.lineage0.generate” was removed ▼ security
- Tool “media.lineage0.status” was removed ▼ security
- Tool “security.diamonize.logs” was removed ▼ security
- Tool “security.diamonize.quarantine” was removed ▼ security
- Tool “security.diamonize.scan” was removed ▼ security
- Tool “security.diamonize.status” was removed ▼ security
- Tool “storage.quezar.delete” was removed ▼ security
- Tool “storage.quezar.list” was removed ▼ security
- Tool “storage.quezar.retrieve” was removed ▼ security
- Tool “storage.quezar.status” was removed ▼ security
- Tool “storage.quezar.store” was removed ▼ security
- Transport: fail → pass ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: io.github.aruuhii2yo/maxion-mcp-gateway → zero-heat-super-compute security
- New tool “storage_quezar_delete”, which the server declares destructive security
- Schema quality: 28 → 41 ▼ functional
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: 60% → 100% ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- The server now declares the “prompts” capability functional
- The server now declares the “resources” capability functional
- First check of Tool coverage: 100 functional
- Schema quality: fair → good functional
- Server version: 16.4.0 → 17.0.0 functional
- New tool “billing_activate” functional
- New tool “billing_purchase” functional
- New tool “engine_maxion_activate” functional
- New tool “engine_maxion_deactivate” functional
- New tool “engine_maxion_diagnostics” functional
- New tool “engine_maxion_status” functional
- New tool “gateway_status” functional
- New tool “media_lineage0_archive” functional
- New tool “media_lineage0_generate” functional
- New tool “media_lineage0_status” functional
- New tool “security_diamonize_logs” functional
- New tool “security_diamonize_quarantine” functional
- New tool “security_diamonize_scan” functional
- New tool “security_diamonize_status” functional
- New tool “storage_quezar_list” functional
- New tool “storage_quezar_retrieve” functional
- New tool “storage_quezar_status” functional
- New tool “storage_quezar_store” functional
- 7 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ 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 5 Nov 2026 · Probed https://5pu357jdkqc3qynzkjvu3okgqy0ncsiy.lambda-url.us-east-1.on.aws/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.lambda-url.us-east-1.on.aws | CN=Amazon RSA 2048 S19,O=Amazon,C=US | 29 Sept 2026 | 15 Apr 2027 | RSA 2048 | SHA256-RSA | 40a712e3d40ea0ec186cb07d6b8eadd5 |
| SANs: *.lambda-url.us-east-1.on.aws | ||||||
| CN=Amazon RSA 2048 S19,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 8 Jul 2026 | 7 Jul 2029 | RSA 2048 | SHA256-RSA | 3e66530c008bab6b9a6d90c1f0d323dac30eeeca |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of 5pu357jdkqc3qynzkjvu3okgqy0ncsiy.lambda-url.us-east-1.on.aws. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| aws. | present | 54182 | 8 | Verified |
| on.aws. | 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 connection |
| HTTP status | 403 |
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://5pu357jdkqc3qynzkjvu3okgqy0ncsiy.lambda-url.us-east-1.on.aws/mcp | Auth required | 403 | |
| http (plaintext) | http://5pu357jdkqc3qynzkjvu3okgqy0ncsiy.lambda-url.us-east-1.on.aws/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 →
billing_activate Activate Gumroad License Key ~86
After completing a Gumroad purchase, call this with your product_permalink and license_key to verify and activate your access. For Lineage.0, the key is consumed after one successful video generation.
| Name | Type | Req | Description |
|---|---|---|---|
| license_key | string | yes | The license key from your Gumroad purchase email. |
| product_permalink | string | yes | The Gumroad product permalink (e.g. 'quezar-monthly'). |
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | – | Activation result and expiration time. |
No examples provided.
billing_purchase Get Trial or Purchase License ~146
Returns a Gumroad checkout link for hourly/monthly access to Maxion/Diamonize/Quezar, or a per-video consumable credit for Lineage.0 ($0.14/sec). Each Lineage.0 key is one-time use -- one key, one video.
| Name | Type | Req | Description |
|---|---|---|---|
| duration | string | yes | For maxion/diamonize/quezar: 'trial' (free 30 min), 'hourly', or 'monthly'. For lineage0: number of seconds (6, 12, 30, 60, or 120) -- each purchase is a single consumable video credit. |
| tool_name | string | yes | The tool namespace to license. |
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | – | License details or checkout URL. |
No examples provided.
engine_maxion_activate Activate Maxion V16 ~64
Activates Maxion V16 and returns live host telemetry: CPU brand, core count, current load, memory usage, and CPU package temperature (where the OS exposes a sensor).
| Name | Type | Req | Description |
|---|---|---|---|
| duration_minutes | number | yes | How long to keep the engine active, in minutes. |
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | – | Telemetry output and activation state. |
No examples provided.
engine_maxion_deactivate Deactivate Maxion V16 ~46
NOT IMPLEMENTED — returns an error. The Maxion engine exposes no deactivate operation, so no governor or power state is changed. Use engine_maxion_status for live telemetry.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | – | Deactivation status message. |
No examples provided.
engine_maxion_diagnostics Maxion V16 Diagnostics ~53
Runs a Maxion V16 diagnostic pass: CPU brand, core count, and total memory for the host system.
| Name | Type | Req | Description |
|---|---|---|---|
| deep_scan | boolean | – | When true, runs extended diagnostics in addition to standard checks. |
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | – | Hardware diagnostic report. |
No examples provided.
engine_maxion_status Maxion V16 Status ~28
Returns Maxion V16's current CPU load and CPU package temperature from the host system.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | – | Current hardware and engine telemetry. |
No examples provided.
gateway_status Gateway System Status ~31
Holistic health overview: all 19 tools, current license status, billing info, and Quezar vault statistics.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | – | System health overview and tool counts. |
No examples provided.
media_lineage0_archive Lineage.0 Media Archive ~27
Lists recently synthesized Lineage.0 multimedia artifacts from the AWS S3 vault.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | – | Archive artifact list. |
No examples provided.
media_lineage0_generate Generate AI Video or Image ~127
4K AI video via Amazon Nova Reel 1.1 or commercial-ready images via Nova Canvas. Polls until synthesis completes and returns a presigned download URL.
| Name | Type | Req | Description |
|---|---|---|---|
| duration | string | – | Required for media_type='video': the purchased credit's duration in seconds. Must match the duration passed to billing_purchase. |
| media_type | string | yes | Output format: 'video' for 4K Nova Reel 1.1 synthesis, 'image' for Nova Canvas commercial-grade image. |
| prompt | string | yes | Natural-language description of the desired video or image content. |
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | – | Generated media URL or synthesis job status. |
No examples provided.
media_lineage0_status Lineage.0 Cluster Status ~28
Real-time status of the Lineage.0 Nova synthesis cluster and S3 vault.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | – | Cluster availability and queue status. |
No examples provided.
security_diamonize_logs Diamonize Security Logs ~65
NOT IMPLEMENTED — returns an error. No interception log is kept, so there are no entries to return and no basis for any verdict about the host.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of recent log entries to return (default 10, max 100). |
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | – | Interception and event log entries. |
No examples provided.
security_diamonize_quarantine Diamonize Quarantine ~66
NOT IMPLEMENTED — returns an error and isolates NOTHING. The Diamonize engine exposes no quarantine operation; a flagged target is left untouched and must be handled by other means.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Absolute file path or process name to record as quarantined. |
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | – | Quarantine action outcome. |
No examples provided.
security_diamonize_scan Diamonize Security Scan ~89
Hashes a target file (SHA-256) on this endpoint. It performs NO signature matching, so it cannot return a clean or infected verdict — the result is always INDETERMINATE. Use the engine-backed stdio gateway for a real scan.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Absolute file path to scan, or the literal string 'SYSTEM_MEMORY' to scan active RAM. |
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | – | Security scan analysis and verdict. |
No examples provided.
security_diamonize_status Diamonize Scanner Status ~41
Reports Diamonize's real posture on this endpoint: no scan engine and no resident shield process run here, so nothing is intercepted or monitored.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | – | Security posture telemetry. |
No examples provided.
storage_quezar_delete Delete Quezar Record ~41
Permanently purges a record from the Quezar Quantum Vault.
| Name | Type | Req | Description |
|---|---|---|---|
| Vault_id | string | yes | The Vault ID of the record to permanently delete. |
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | – | Deletion confirmation message. |
No examples provided.
storage_quezar_list List Quezar Sectors ~25
Lists all encrypted sector IDs currently stored in the Quezar Quantum Vault.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | – | List of active sector IDs. |
No examples provided.
storage_quezar_retrieve Retrieve Quezar Data ~46
Decrypts and retrieves a payload from the Quezar Quantum Vault by Vault ID.
| Name | Type | Req | Description |
|---|---|---|---|
| Vault_id | string | yes | The Vault ID returned when the data was stored. |
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | – | Decrypted payload. |
No examples provided.
storage_quezar_status Quezar Storage Status ~25
Quezar telemetry: sector count, vault size, and encryption stats.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | – | Vault storage metrics. |
No examples provided.
storage_quezar_store Store Data in Quezar ~61
Encrypts and stores a payload in the Quezar Quantum Vault using AES-256-GCM. Returns a Vault ID for retrieval.
| Name | Type | Req | Description |
|---|---|---|---|
| payload | string | yes | Plain-text data to encrypt and store. Accepts any string up to 10 MB. |
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | – | Stored sector ID and encryption metadata. |
No examples provided.
How do I install the io.github.aruuhii2yo/maxion-mcp-gateway server?
io.github.aruuhii2yo/maxion-mcp-gateway is a hosted endpoint at https://5pu357jdkqc3qynzkjvu3okgqy0ncsiy.lambda-url.us-east-1.on.aws/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 · 5pu357jdkqc3qynzkjvu3okgqy0ncsiy.lambda-url.us-east-1.on.aws
claude mcp add --transport http aruuhii2yo-maxion-mcp-gateway 'https://5pu357jdkqc3qynzkjvu3okgqy0ncsiy.lambda-url.us-east-1.on.aws/mcp'
What is the io.github.aruuhii2yo/maxion-mcp-gateway server?
io.github.aruuhii2yo/maxion-mcp-gateway is listed in the public MCP registry as io.github.aruuhii2yo/maxion-mcp-gateway. CPU telemetry & benchmarking, SHA-256 hashing, AES-256-GCM storage, AI video/image via Nova. This page covers its hosted endpoint (https://5pu357jdkqc3qynzkjvu3okgqy0ncsiy.lambda-url.us-east-1.on.aws/mcp).
Is the io.github.aruuhii2yo/maxion-mcp-gateway server safe to use?
io.github.aruuhii2yo/maxion-mcp-gateway scores 33 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 io.github.aruuhii2yo/maxion-mcp-gateway server expose?
io.github.aruuhii2yo/maxion-mcp-gateway exposes 19 tools: engine_maxion_activate, engine_maxion_deactivate, engine_maxion_status, engine_maxion_diagnostics, security_diamonize_scan, and 14 more. Their descriptions and schemas cost roughly 1,095 tokens of context every time the server is loaded.
Does the io.github.aruuhii2yo/maxion-mcp-gateway server require authentication?
Yes. io.github.aruuhii2yo/maxion-mcp-gateway 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 io.github.aruuhii2yo/maxion-mcp-gateway server still maintained?
io.github.aruuhii2yo/maxion-mcp-gateway is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.