VNISH Global Operator
REMOTE · VNISH.GLOBAL
Read-only VNISH firmware metadata, Ninja guidance and input-based mining economics calculations.
Available components
Last scanned (18 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability43
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 511 tokens (~85/item across 6 items; 3 tools + 3 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 Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 64% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 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
- 24 Oct 26 +1
- Stability: 0.97 → pass security
- 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
- 24 Sept 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 21 Nov 2026 · Probed https://vnish.global/ai/mcp/index.php
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vnish.global | CN=YE1,O=Let's Encrypt,C=US | 23 Oct 2026 | 21 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 52af27f3934b7887fb6a99d91bcee01241d |
| SANs: vnish.global, www.vnish.global | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of vnish.global. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| global. | DS published | 52924 | 8 | Verified |
| vnish.global. | No DS | 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=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; base-uri 'self'; form-action 'self' mailto:; frame-ancestors 'none'; object-src 'none'; script-src 'self'; style-src 'self'; img-src 'self' data:; font-src 'self'; connect-src 'self'; media-src 'self'; manifest-src 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vnish.global/ai/mcp/index.php | Verified | 200 | |
| http (plaintext) | http://vnish.global/ai/mcp/index.php | HTTPS enforced | 301 | https://vnish.global/ai/mcp/index.php |
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 →
calculate_roi_scenario Calculate an ROI ASIC daily scenario ~254
Calculate hypothetical daily revenue after an illustrative time/hashrate-based developer fee and electricity cost using user-supplied inputs. H*q*(hours/24)*(1-f/100) - (W/1000)*hours*t. This is a scenario, not a profit forecast or a statement of actual VNISH fees. Use pre-fee gross hashrate; do not deduct the fee twice.
| Name | Type | Req | Description |
|---|---|---|---|
| dev_fee_percent | number | yes | Scenario fee as a percent of gross daily revenue. This tool does not supply an actual firmware fee. |
| electricity_usd_per_kwh | number | yes | Electricity price in USD/kWh. |
| hashprice_usd_per_th_day | number | yes | Gross daily revenue for one TH/s, USD/(TH/s)/day. Supply it yourself; no market data is fetched. |
| hashrate_th_s | number | yes | Gross pre-fee hashrate, TH/s. The daily hashprice input must use the same hashrate basis. |
| operating_hours_per_day | number | – | Hours per day at the stated hashrate and wall power. Revenue and electricity scale by this same uptime assumption. |
| power_w | number | yes | Average wall power while operating, watts. |
No output schema declared.
No examples provided.
find_ninja_reference Find a VNISH Ninja reference ~67
Return a selected public VNISH Ninja guide about control-board identification, installation SSH errors, or return-to-stock preparation. A reference is not a device-specific installation or recovery instruction. No device connection or action is performed.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| topic | string | yes | – |
No output schema declared.
No examples provided.
lookup_firmware Look up a VNISH Global catalog record ~118
Find records in a dated snapshot of the public vnish.global firmware catalog. Use the exact model ID; narrow by board code and version if known. Returns file size, SHA-256 and source links. A catalog record does not establish device compatibility, package authenticity, or successful hardware testing. Does not download or install firmware.
| Name | Type | Req | Description |
|---|---|---|---|
| board_platform | string | – | – |
| model_id | string | yes | Exact catalog model ID, for example s19j-xp. Read the model-index resource for all IDs. |
| version | string | – | – |
No output schema declared.
No examples provided.
How do I install the VNISH Global Operator MCP server?
VNISH Global Operator is a hosted endpoint at https://vnish.global/ai/mcp/index.php, 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 · vnish.global
claude mcp add --transport http vnish-global-vnish-global-operator 'https://vnish.global/ai/mcp/index.php'
What is the VNISH Global Operator MCP server?
VNISH Global Operator is an MCP server listed in the public MCP registry as io.github.vnish-global/vnish-global-operator. Read-only VNISH firmware metadata, Ninja guidance and input-based mining economics calculations. This page covers its hosted endpoint (https://vnish.global/ai/mcp/index.php).
Is the VNISH Global Operator MCP server safe to use?
VNISH Global Operator 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 VNISH Global Operator MCP server expose?
VNISH Global Operator exposes 3 tools: lookup_firmware, find_ninja_reference, calculate_roi_scenario. Their descriptions and schemas cost roughly 439 tokens of context every time the server is loaded.
Does the VNISH Global Operator MCP server require authentication?
No. We connected to VNISH Global Operator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the VNISH Global Operator MCP server still maintained?
VNISH Global Operator is still listed as active in the MCP registry. We last reached this channel on 21 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 VNISH Global Operator MCP server?
VerifyMCP ran 13 checks on VNISH Global Operator, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.