Nodehour: GPU and accelerator capacity by chip, count, term and region
REMOTE · NODEHOUR.FOREVENZA.COM
GPU and accelerator capacity by chip, count, term, region and interconnect, specified to source.
Available components
Last scanned (23 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Cloud Infrastructure
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 Security63
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 305 tokens (~101/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 36% 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 4 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
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 4 Nov 26 62
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 4 Nov 2026 · Probed https://nodehour.forevenza.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=forevenza.com | CN=WE1,O=Google Trust Services,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 13a6eff8c05803dc0e4a2421fea40769 |
| SANs: forevenza.com, nodehour.forevenza.com, *.nodehour.forevenza.com | ||||||
| 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 nodehour.forevenza.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| forevenza.com. | absent | 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 |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nodehour.forevenza.com/mcp | Verified | 200 | |
| http (plaintext) | http://nodehour.forevenza.com/mcp | Inconclusive | 405 |
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 →
describe_proposition Describe a service ~42
Everything about one service: what happens to a request, what you get, scope and limits, the request fields and any operations.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
list_propositions List Nodehour's services ~32
List Nodehour's services with a one-line summary: lookups that run instantly, and requirements you can send.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_request Send a requirement ~126
Send a requirement to one of Nodehour's services. It is kept with a reference number.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| budget | object | – | – |
| contact | object | – | Optional; stored apart and deleted after 180 days |
| geography | object | – | – |
| need | string | yes | The requirement in words |
| quantity | object | – | – |
| requested_fields | array | – | – |
| slug | string | yes | Service slug, or anything-else |
| specifications | object | – | Fields from the service's request schema |
| timing | object | – | – |
No output schema declared.
No examples provided.
How do I install the Nodehour: GPU and accelerator capacity by chip, count… MCP server?
Nodehour: GPU and accelerator capacity by chip, count… is a hosted endpoint at https://nodehour.forevenza.com/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 · nodehour.forevenza.com
claude mcp add --transport http com-forevenza-services-nodehour 'https://nodehour.forevenza.com/mcp'
What is the Nodehour: GPU and accelerator capacity by chip, count… MCP server?
Nodehour: GPU and accelerator capacity by chip, count… is an MCP server listed in the public MCP registry as com.forevenza.services/nodehour. GPU and accelerator capacity by chip, count, term, region and interconnect, specified to source. This page covers its hosted endpoint (https://nodehour.forevenza.com/mcp).
Is the Nodehour: GPU and accelerator capacity by chip, count… MCP server safe to use?
Nodehour: GPU and accelerator capacity by chip, count… scores 62 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 Nodehour: GPU and accelerator capacity by chip, count… MCP server expose?
Nodehour: GPU and accelerator capacity by chip, count… exposes 3 tools: list_propositions, describe_proposition, submit_request. Their descriptions and schemas cost roughly 200 tokens of context every time the server is loaded.
Does the Nodehour: GPU and accelerator capacity by chip, count… MCP server require authentication?
No. We connected to Nodehour: GPU and accelerator capacity by chip, count… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Nodehour: GPU and accelerator capacity by chip, count… MCP server still maintained?
Nodehour: GPU and accelerator capacity by chip, count… is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.