# io.github.Pak209/alphalabs-intelligence (remote · api.pak-labs.com)

Live trading-pipeline intelligence for AI agents: signal scoring, calibration, recorded outcomes.

- Trust score: 57/100 (low)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.pak-labs.com`: 57/100 (this document), [markdown](https://verifymcp.io/servers/pak209-alphalabs-intelligence/api.md), [page](https://verifymcp.io/servers/pak209-alphalabs-intelligence/api)

## Channel facts

- Endpoint: `https://api.pak-labs.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - 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**: 60/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 423 tokens (~70/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http pak209-alphalabs-intelligence https://api.pak-labs.com/mcp
```

### Codex

```toml
[mcp_servers.pak209-alphalabs-intelligence]
url = "https://api.pak-labs.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pak209-alphalabs-intelligence": {
      "type": "remote",
      "url": "https://api.pak-labs.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pak209-alphalabs-intelligence --url https://api.pak-labs.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  pak209-alphalabs-intelligence:
    url: "https://api.pak-labs.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "pak209-alphalabs-intelligence": {
      "type": "http",
      "url": "https://api.pak-labs.com/mcp"
    }
  }
}
```

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-08-03 (score 57, +1)

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

### 2026-08-01 (score 56, +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-07-31 (score 55, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 56, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 57, +1)

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

### 2026-07-27 (score 56, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 55)

First indexed and scored.

## MCP tools (6)

### `alphalabs_get_catalog` (~25 tokens)

Free: list AlphaLabs Intelligence products, prices, and auth model.

### `alphalabs_calibration_report` (~47 tokens)

Live paper-trading pipeline calibration telemetry: stage funnel, gate failures, near-misses. Derived analytics only — no positions, orders, or account data exist on this surface.

### `alphalabs_evaluate_signal` (~166 tokens)

Score YOUR trade idea through the live AlphaLabs deterministic engine: composite score, tier, per-component sub-signals, floors. Price/volume confirmation is not evaluated (no vendor market data). Returns an evaluation_id for alphalabs_explain_decision.

Input parameters:

- `bias` (string, required)
- `catalyst` (string): What just happened (headline/event)
- `catalyst_score` (number): Optional 0-100 materiality if you scored it
- `catalyst_type` (string): Optional label, e.g. 'Government Contract'
- `confidence` (number): Your own conviction 0-1 (echoed, not scored)
- `thesis` (string): Why it should move the stock
- `ticker` (string, required): Symbol, e.g. NVDA

### `alphalabs_outcome_report` (~53 tokens)

Recorded outcomes of the live pipeline's own decisions: hit rates, score-band tables, accepted-vs-rejected edge, gate near-miss regret. Aggregated engine telemetry — percent moves and counts only.

### `alphalabs_feature_attribution` (~38 tokens)

Which engine inputs actually predict outcomes, measured on recorded live results: Spearman rankings, median-split deltas, dead inputs.

### `alphalabs_explain_decision` (~46 tokens)

Glass-box breakdown of a prior evaluation by evaluation_id: every sub-signal, weight, floor, and the composite reasoning.

Input parameters:

- `evaluation_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/pak209-alphalabs-intelligence/api#diagnostics

## Score history

- 2026-08-03: 57
- 2026-08-02: 56
- 2026-08-01: 56
- 2026-07-31: 55
- 2026-07-30: 56
- 2026-07-29: 57
- 2026-07-28: 57
- 2026-07-27: 56
- 2026-07-26: 55

## Links

- Remote endpoint: https://api.pak-labs.com/mcp
- Website: https://api.pak-labs.com/
- Changelog RSS feed: https://verifymcp.io/servers/pak209-alphalabs-intelligence/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/pak209-alphalabs-intelligence/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/pak209-alphalabs-intelligence/api