Hybrid Recursive Ladder
PYPI · HYBRID-RECURSIVE-LADDER-MCP
Aggregate long time-series ranges with a few source requests instead of one per bucket.
Available components
Last scanned (19 hours ago)
Scores higher than 60% of PyPI servers
Category Data and Analytics
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 → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 2 dependencies flagged as unhealthy. 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 Usability52
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 317 tokens (~79/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 49
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 4 Nov 2026 · Analysed pypi/hybrid-recursive-ladder-mcp@0.0.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 2 packages
| Packages resolved | 2 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
ladder_decompose Decompose a time range ~79
Decompose [start, end) into month/day/hour/minute ladder segments. Times accept ISO-8601 (``2026-01-01T00:00:00``) or epoch milliseconds.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | – |
| finest | string | – | – |
| start | string | yes | – |
| timezone | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
ladder_meta Ladder metadata ~20
Return version, configuration, source/store type and demo range.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
ladder_sum Sum time series ~135
Sum time series over a range. ``series`` items use ``{"entity": "...", "key": "...", "name": "..."}`` (``device_id``/``device_name`` are accepted as aliases). ``mode`` is ``tb`` (source only), ``mixed`` (local first) or ``local`` (offline). With no series, the built-in demo series are used.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | – |
| finest | string | – | – |
| materialize | boolean | – | – |
| mode | string | – | – |
| series | array | yes | – |
| start | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
ladder_verify Verify against source ~83
Compare the authoritative source with the local store. Returns per-segment differences and, for the first ``drill_limit`` differing segments, point-level added/removed/changed counts.
| Name | Type | Req | Description |
|---|---|---|---|
| drill_limit | integer | – | – |
| end | string | yes | – |
| finest | string | – | – |
| series | array | yes | – |
| start | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Hybrid Recursive Ladder MCP server?
Hybrid Recursive Ladder runs locally as a PyPI package, launched with uvx hybrid-recursive-ladder-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · hybrid-recursive-ladder-mcp
claude mcp add magicsquarekey-hybrid-recursive-ladder -- uvx hybrid-recursive-ladder-mcp
What is the Hybrid Recursive Ladder MCP server?
Hybrid Recursive Ladder is an MCP server listed in the public MCP registry as io.github.MagicSquarekey/hybrid-recursive-ladder. Aggregate long time-series ranges with a few source requests instead of one per bucket. This page covers its PyPI package (hybrid-recursive-ladder-mcp).
Is the Hybrid Recursive Ladder MCP server safe to use?
Hybrid Recursive Ladder scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. 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 Hybrid Recursive Ladder MCP server expose?
Hybrid Recursive Ladder exposes 4 tools: ladder_meta, ladder_decompose, ladder_sum, ladder_verify. Their descriptions and schemas cost roughly 317 tokens of context every time the server is loaded.
Is the Hybrid Recursive Ladder MCP server still maintained?
Hybrid Recursive Ladder is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Hybrid Recursive Ladder MCP server under?
Hybrid Recursive Ladder declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.