# SCRIPTMASTERLABS — PRO-LO (remote · pro-lo.onrender.com)

Coherence-gated signal engine. Paid verdict settled end-to-end 2026-11-01 (SELF-PROOF, XRPL).

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `pro-lo.onrender.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-scriptmasterlabs-pro-lo/api-mcp-rpc.md), [page](https://verifymcp.io/servers/com-scriptmasterlabs-pro-lo/api-mcp-rpc)

## Channel facts

- Endpoint: `https://pro-lo.onrender.com/api/mcp/rpc`
- Transports: `streamable-http`
- Auth: `none`
- Version: `3.1.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1352 tokens (~112/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_gemini_frontier_reasoning" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the SCRIPTMASTERLABS — PRO-LO MCP server?

SCRIPTMASTERLABS — PRO-LO is a hosted endpoint at https://pro-lo.onrender.com/api/mcp/rpc, 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.

### Claude

```bash
claude mcp add --transport http com-scriptmasterlabs-pro-lo 'https://pro-lo.onrender.com/api/mcp/rpc'
```

### Cursor

```json
{
  "mcpServers": {
    "com-scriptmasterlabs-pro-lo": {
      "url": "https://pro-lo.onrender.com/api/mcp/rpc"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-scriptmasterlabs-pro-lo": {
      "type": "http",
      "url": "https://pro-lo.onrender.com/api/mcp/rpc"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-scriptmasterlabs-pro-lo]
url = "https://pro-lo.onrender.com/api/mcp/rpc"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-scriptmasterlabs-pro-lo": {
      "type": "remote",
      "url": "https://pro-lo.onrender.com/api/mcp/rpc",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-scriptmasterlabs-pro-lo --url 'https://pro-lo.onrender.com/api/mcp/rpc' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-scriptmasterlabs-pro-lo:
    url: "https://pro-lo.onrender.com/api/mcp/rpc"
```

### Netclaw

```json
{
  "McpServers": {
    "com-scriptmasterlabs-pro-lo": {
      "Transport": "http",
      "Url": "https://pro-lo.onrender.com/api/mcp/rpc"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-scriptmasterlabs-pro-lo -t streamable-http -u 'https://pro-lo.onrender.com/api/mcp/rpc'
```

### Other

```json
{
  "mcpServers": {
    "com-scriptmasterlabs-pro-lo": {
      "type": "http",
      "url": "https://pro-lo.onrender.com/api/mcp/rpc"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 70, +8)

- [security improvement] Authorization: unverified → partial

### 2026-10-28 (score 62, 0)

- [security] Tool “classify_microstructure_regime” rewrote its description, which is the text the model reads
- [security] Tool “coherence_jev_verdict” rewrote its description, which is the text the model reads
- [security] Tool “track_gamma_squeeze_mechanics” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “earnings_gate_verdict”

### 2026-10-27 (score 62)

First indexed and scored.

## MCP tools (12)

### `analyze_narrative_divergence` (~111 tokens)

Compares real fundamental signals (P/E, real reference data) against a disclosed, real-price-derived momentum/volatility proxy for narrative intensity. Real fundamental/social sentiment data is not currently wired — narrative-side scoring is disclosed as a proxy, not literal sentiment measurement.

Input parameters:

- `ticker` (string, required): Stock ticker symbol (e.g. NVDA, TSLA, AAPL, MSFT)
- `timeHorizonDays` (number): Lookback window in days (default: 90)

### `simulate_counterfactual_stress_test` (~78 tokens)

Runs a disclosed hypothetical shock scenario (from a static, pre-defined scenario catalog) against a real live quote. The projected impact is an explicit heuristic model applied to a real spot price, not a claimed prediction.

Input parameters:

- `scenarioId` (string, required): Pre-configured scenario ID
- `ticker` (string, required): Target ticker symbol

### `classify_microstructure_regime` (~65 tokens)

Real dealer gamma exposure (GEX) computed from a real fetched options chain (Tradier/Polygon), and Reg SHO threshold-list status from the SEC fails-to-deliver record via the SqueezeOS FTD oracle.

Input parameters:

- `ticker` (string, required): Stock ticker symbol

### `execute_gemini_frontier_reasoning` (~67 tokens)

Invokes Google Gemini with real, live-fetched market data as grounding context — no invented inputs are passed to the model.

Input parameters:

- `focusQuestion` (string): Specific analytical thesis or strategic question to investigate
- `ticker` (string, required): Target ticker or asset name

### `generate_trade_execution_signals` (~118 tokens)

Generates a disclosed-heuristic BUY/SELL/HOLD verdict and selects real, currently-listed option contracts (real strike, real expiration, real bid/ask/greeks) nearest a target delta band from a real fetched chain — never an invented contract.

Input parameters:

- `ticker` (string, required): Stock ticker symbol (e.g., NVDA, AAPL, TSLA, MSFT)
- `timeHorizon` (string): Target trading horizon (e.g., "14_days", "30_days", "45_days", "90_days")

### `mandelbrot_fractal_analysis` (~113 tokens)

Real Rescaled-Range Hurst exponent computed from real historical bars at each real timeframe (15M/1H/4H/1D/1W). Reports real excess kurtosis of the real return series. Does not compute a true Hölder singularity spectrum (requires tick-level history this build does not ingest) — abstains rather than fabricating one.

Input parameters:

- `ticker` (string, required): Stock ticker symbol (e.g. NVDA, TSLA, AMC, GME, SPY)

### `track_volatility_surface` (~58 tokens)

Real implied-volatility surface grid built directly from a real fetched options chain across several real expirations — every grid point is a real listed contract, not an interpolated/fabricated one.

Input parameters:

- `ticker` (string, required): Stock ticker symbol

### `track_gamma_squeeze_mechanics` (~61 tokens)

Real squeeze-pressure score from real chain-derived GEX and SEC fails-to-deliver pressure via the SqueezeOS FTD oracle — a disclosed proxy for short-selling pressure, not true short interest.

Input parameters:

- `ticker` (string, required): Stock ticker symbol

### `live_universe_scanner_scan` (~83 tokens)

Real wide-market scan (Polygon grouped-daily aggregates across the real US equity universe, not a fixed short symbol list, no pinned symbols) fused with the real per-symbol GEX/Hurst/IV-surface engines above.

Input parameters:

- `filterRegime` (string): Filter criteria: ALL, SQUEEZE, FRACTAL, SKEW

### `coherence_gate_review` (~116 tokens)

PRO-LO Coherence Gate: multi-path consensus for one ticker across PRO-LO's independent real directional signals (trade-engine composite, daily SMA20/50 trend, SqueezeOS graded picks, SML Triple-Trigger). Returns each path with direction (long/short/flat) and confidence, the coherence score, and pass/block gate. Same formula as the SML mcp-x402 Coherent Gate. Jev (TypeSafe) review is not run over MCP.

Input parameters:

- `ticker` (string, required): Stock ticker symbol

### `coherence_jev_verdict` (~224 tokens)

Paid (x402, 0.25 RLUSD) read-only decision product: computes PRO-LO multi-path coherence for a ticker — coherence = |Σ w·d| / Σ w across the signal paths (paths that cannot answer abstain and never vote) — and adds a Jev (TypeSafe AI) review. Verdict is PASS when consensus is non-flat, coherence >= 0.6, at least 2 paths agree, and the agreeing paths span at least 2 distinct data families (the trade composite and daily trend share the price series = one family); otherwise DENY, with a family-blocked DENY naming that reason. Jev review reports status unavailable when TYPESAFE_API_KEY is not configured — never simulated.

Input parameters:

- `action` (string): Optional proposed action this verdict is about (context, echoed back in the result)
- `claim` (string): Optional claim or context being evaluated (echoed back in the result)
- `ticker` (string, required): Stock ticker symbol (e.g. NVDA, AMC, GME)

### `earnings_gate_verdict` (~258 tokens)

Paid (x402, 0.25 RLUSD) pre-earnings coherence gate: four paths across three data families — SEC EDGAR insider Form 4 open-market direction, SEC fails-to-deliver pressure (SqueezeOS FTD oracle), front-expiration options flow imbalance, and dealer gamma-exposure structure (flow and structure are measured from one chain snapshot = one family) — vote into the fleet coherence formula coherence = |Σ w·d| / Σ w. Verdict is PASS when consensus is non-flat, coherence >= 0.6, at least 2 paths agree, and the agreeing paths span at least 2 distinct data families; otherwise DENY. Paths that cannot answer abstain and are named in the output — they never vote. Includes a Jev (TypeSafe AI) review (status unavailable when not configured — never simulated). SHADOW posture: decision_eligible is false; the gate executes nothing.

Input parameters:

- `earnings_date` (string): Optional earnings print date (YYYY-MM-DD) to anchor the gate; when omitted, the next real print is read from the Finnhub earnings calendar
- `ticker` (string, required): Stock ticker symbol (e.g. NVDA, AAPL, TSLA)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-scriptmasterlabs-pro-lo/api-mcp-rpc#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 72
- 2026-11-03: 72
- 2026-11-02: 72
- 2026-11-01: 71
- 2026-10-31: 71
- 2026-10-30: 70
- 2026-10-29: 70
- 2026-10-28: 62
- 2026-10-27: 62

## Common questions

### What is the SCRIPTMASTERLABS — PRO-LO MCP server?

SCRIPTMASTERLABS — PRO-LO is an MCP server listed in the public MCP registry as com.scriptmasterlabs/pro-lo. Coherence-gated signal engine. Paid verdict settled end-to-end 2026-11-01 (SELF-PROOF, XRPL). This page covers its hosted endpoint (https://pro-lo.onrender.com/api/mcp/rpc).

### Is the SCRIPTMASTERLABS — PRO-LO MCP server safe to use?

SCRIPTMASTERLABS — PRO-LO scores 73 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 SCRIPTMASTERLABS — PRO-LO MCP server expose?

SCRIPTMASTERLABS — PRO-LO exposes 12 tools: analyze_narrative_divergence, simulate_counterfactual_stress_test, classify_microstructure_regime, execute_gemini_frontier_reasoning, generate_trade_execution_signals, and 7 more. Their descriptions and schemas cost roughly 1,352 tokens of context every time the server is loaded.

### Does the SCRIPTMASTERLABS — PRO-LO MCP server require authentication?

No. We connected to SCRIPTMASTERLABS — PRO-LO without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SCRIPTMASTERLABS — PRO-LO MCP server still maintained?

SCRIPTMASTERLABS — PRO-LO 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.

## Links

- Remote endpoint: https://pro-lo.onrender.com/api/mcp/rpc
- Website: https://www.scriptmasterlabs.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-scriptmasterlabs-pro-lo/api-mcp-rpc.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-scriptmasterlabs-pro-lo/api-mcp-rpc.json
- HTML version of this page: https://verifymcp.io/servers/com-scriptmasterlabs-pro-lo/api-mcp-rpc