Nexus Alpha Geometry
REMOTE · NEXUS.ROGUEFRONTIERVC.COM
Finance research agent for thesis, trade note, and market-state review.
Available components
Last scanned (22 hours ago)
Scores higher than 18% 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
- 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 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.
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 fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
- 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 →
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.
- 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
- 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
- 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
- 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
- 7 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.37 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Jul 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
- 30 Jul 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
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://nexus.roguefrontiervc.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nexus.roguefrontiervc.com | CN=YR2,O=Let's Encrypt,C=US | 25 Oct 2026 | 23 Jan 2027 | RSA 2048 | SHA256-RSA | 63b7b1afe8d74b13eb4e402b2e2fc25a22c |
| SANs: nexus.roguefrontiervc.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of nexus.roguefrontiervc.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| roguefrontiervc.com. | 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=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nexus.roguefrontiervc.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://nexus.roguefrontiervc.com/api/mcp | HTTPS enforced | 308 | https://nexus.roguefrontiervc.com/api/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 →
generate_alpha_geometry_review Generate Alpha Geometry Review ~227
Generate a public-safe Nexus Alpha Geometry review from a user-provided thesis, single ticker, or basket/watchlist. Handles single-symbol and multi-symbol basket input, default relative benchmarks, market-pressure context, basket geometry, credit/rates nuance, meta-factor pressure, and thesis tracking. Research only; no trade signals, financial advice, position sizing, or order routing.
| Name | Type | Req | Description |
|---|---|---|---|
| decisionContext | string | – | The decision context the user wants to clarify. Output remains documentation-only. |
| instrument | string | – | Ticker, instrument, or comma/space-separated basket symbols such as TSLA,NVDA,SPY,QQQ. |
| note | string | yes | The user-provided market note, thesis, report excerpt, or portfolio/basket concern. |
| relativeBenchmark | string | – | Optional benchmark or comparison context. Single-symbol mode defaults to SPY, QQQ, and mapped sector benchmark when omitted; basket mode also uses default benchmarks where needed. |
| reviewType | string | – | The type of input being reviewed. |
| timeframe | string | – | Optional timeframe associated with the note. |
No output schema declared.
No examples provided.
How do I install the Nexus Alpha Geometry MCP server?
Nexus Alpha Geometry is a hosted endpoint at https://nexus.roguefrontiervc.com/api/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 · nexus.roguefrontiervc.com
claude mcp add --transport http spearmanmode-nexus-alpha-geometry 'https://nexus.roguefrontiervc.com/api/mcp'
What is the Nexus Alpha Geometry MCP server?
Nexus Alpha Geometry is an MCP server listed in the public MCP registry as io.github.SpearmanMODE/nexus-alpha-geometry. Finance research agent for thesis, trade note, and market-state review. This page covers its hosted endpoint (https://nexus.roguefrontiervc.com/api/mcp).
Is the Nexus Alpha Geometry MCP server safe to use?
Nexus Alpha Geometry scores 35 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 Nexus Alpha Geometry MCP server expose?
Nexus Alpha Geometry exposes 1 tool: generate_alpha_geometry_review. Their descriptions and schemas cost roughly 227 tokens of context every time the server is loaded.
Does the Nexus Alpha Geometry MCP server require authentication?
No. We connected to Nexus Alpha Geometry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Nexus Alpha Geometry MCP server still maintained?
Nexus Alpha Geometry 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 Nexus Alpha Geometry MCP server?
VerifyMCP ran 5 checks on Nexus Alpha Geometry, 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 Nexus Alpha Geometry: 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.