XCREENER
NPM · @XCREENER/MCP · SCANNED AUG 15
Local stdio MCP bridge for XCREENER's XQL screener API — validate, explain, and run queries.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 506 tokens (~126/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @xcreener/mcp
claude mcp add com-xcreener-xcreener-mcp -- npx -y @xcreener/mcp
codex mcp add com-xcreener-xcreener-mcp -- npx -y @xcreener/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-xcreener-xcreener-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@xcreener/mcp"
],
"enabled": true
}
}
} openclaw mcp add com-xcreener-xcreener-mcp --command npx --arg -y --arg @xcreener/mcp
mcp_servers:
com-xcreener-xcreener-mcp:
command: "npx"
args: ["-y", "@xcreener/mcp"] {
"mcpServers": {
"com-xcreener-xcreener-mcp": {
"command": "npx",
"args": [
"-y",
"@xcreener/mcp"
]
}
}
} 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.
- 15 Aug 26 +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.
- 14 Aug 26 +3
- Stability: unverified → 0.23 ▲ functional
- 11 Aug 26 +2
- 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 68
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 15 Aug 2026 · Analysed npm/@xcreener/mcp@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
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.
xql_explain ~40
Parse and plan an XQL query, returning its execution plan and a human-readable explanation.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Raw XQL query text |
No output schema declared.
No examples provided.
xql_nl_reference ~93
Fetch the XQL natural-language reference document, mapping retail-trader phrasing to valid XQL syntax and documenting hard limits (300-bar lookback ceiling, closed market/timeframe enums, the atr no-source-argument exception, etc.). Call this before writing a query, or after xql_validate/xql_explain/xql_run returns isError: true, to see the exact construct you likely got wrong.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
xql_run ~63
Parse, plan, and execute an XQL query against live market data, returning matching instruments. Call xql_validate on the query first to catch syntax errors before spending a live-data round trip on this call.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Raw XQL query text |
No output schema declared.
No examples provided.
xql_validate ~39
Validate XQL query text by parsing and planning it, without executing it against live data.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Raw XQL query text |
No output schema declared.
No examples provided.