io.github.Pak209/alphalabs-intelligence
REMOTE · API.PAK-LABS.COM · SCANNED SEP 20
Live trading-pipeline intelligence for AI agents: signal scoring, calibration, recorded outcomes.
Available components
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 Security46
- 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 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. See how to fix → View diagnostics → Unverified
- 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 Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 423 tokens (~70/item across 6 items; 6 tools + 0 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 Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.Pak209/alphalabs-intelligence MCP server?
io.github.Pak209/alphalabs-intelligence is a hosted endpoint at https://api.pak-labs.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 · api.pak-labs.com
claude mcp add --transport http pak209-alphalabs-intelligence 'https://api.pak-labs.com/mcp'
{
"mcpServers": {
"pak209-alphalabs-intelligence": {
"url": "https://api.pak-labs.com/mcp"
}
}
} {
"servers": {
"pak209-alphalabs-intelligence": {
"type": "http",
"url": "https://api.pak-labs.com/mcp"
}
}
} [mcp_servers.pak209-alphalabs-intelligence] url = "https://api.pak-labs.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pak209-alphalabs-intelligence": {
"type": "remote",
"url": "https://api.pak-labs.com/mcp",
"enabled": true
}
}
} openclaw mcp add pak209-alphalabs-intelligence --url 'https://api.pak-labs.com/mcp' --transport streamable-http
mcp_servers:
pak209-alphalabs-intelligence:
url: "https://api.pak-labs.com/mcp" {
"McpServers": {
"pak209-alphalabs-intelligence": {
"Transport": "http",
"Url": "https://api.pak-labs.com/mcp"
}
}
} assistant mcp add pak209-alphalabs-intelligence -t streamable-http -u 'https://api.pak-labs.com/mcp'
{
"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.
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.
- 30 Aug 26 +53
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: 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. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 27 Aug 26 −53
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 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 20 Sept 2026 · Probed https://api.pak-labs.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pak-labs.com | CN=WE1,O=Google Trust Services,C=US | 16 Aug 2026 | 14 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | f34797e15050e5691377550f669c362d |
| SANs: pak-labs.com, *.pak-labs.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 api.pak-labs.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| pak-labs.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.pak-labs.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.pak-labs.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 →
alphalabs_calibration_report ~47
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
alphalabs_evaluate_signal ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bias | string | yes | – |
| 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 | yes | Symbol, e.g. NVDA |
No output schema declared.
No examples provided.
alphalabs_explain_decision ~46
Glass-box breakdown of a prior evaluation by evaluation_id: every sub-signal, weight, floor, and the composite reasoning.
| Name | Type | Req | Description |
|---|---|---|---|
| evaluation_id | string | yes | – |
No output schema declared.
No examples provided.
alphalabs_feature_attribution ~38
Which engine inputs actually predict outcomes, measured on recorded live results: Spearman rankings, median-split deltas, dead inputs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
alphalabs_get_catalog ~25
Free: list AlphaLabs Intelligence products, prices, and auth model.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
alphalabs_outcome_report ~53
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.Pak209/alphalabs-intelligence MCP server?
io.github.Pak209/alphalabs-intelligence is an MCP server listed in the public MCP registry as io.github.Pak209/alphalabs-intelligence. Live trading-pipeline intelligence for AI agents: signal scoring, calibration, recorded outcomes. This page covers its hosted endpoint (https://api.pak-labs.com/mcp).
Is the io.github.Pak209/alphalabs-intelligence MCP server safe to use?
io.github.Pak209/alphalabs-intelligence scores 71 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 io.github.Pak209/alphalabs-intelligence MCP server expose?
io.github.Pak209/alphalabs-intelligence exposes 6 tools: alphalabs_get_catalog, alphalabs_calibration_report, alphalabs_evaluate_signal, alphalabs_outcome_report, alphalabs_feature_attribution, alphalabs_explain_decision. Their descriptions and schemas cost roughly 375 tokens of context every time the server is loaded.
Does the io.github.Pak209/alphalabs-intelligence MCP server require authentication?
No. We connected to io.github.Pak209/alphalabs-intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.Pak209/alphalabs-intelligence MCP server still maintained?
io.github.Pak209/alphalabs-intelligence is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.